Open forgetso opened 4 years ago
Or are there much bigger changes to spacy that will require a rewrite of sense2vec?
Yep, this is the case ;-)
There have been quite some refactors, new & moved functionality in v.3. So I wouldn't be surprised at all if sense2vec
will require a rewrite once a stable version of spaCy 3 is out...
Is there any way to get sense2vec working with spacy nightly? Upon importing sense2vec I get the following error:
Has component been renamed to something else in spacy v3? Or are there much bigger changes to spacy that will require a rewrite of sense2vec?