-
Notifications
You must be signed in to change notification settings - Fork 857
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include support for spaCy v3 #1621
Comments
@henryre Sounds reasonable. I'm interested in doing this work. I'm looking at the spaCy v3 migration docs and I have a couple of questions:
If you aren't sure, I can figure the answers out myself, but it doesn't look like a difficult migration based on the spacy code I've read in Snorkel in the past. |
@rjurney agreed, shouldn't be too difficult. The library isn't very opinionated about spaCy usage, so I don't expect any of the above to come into play. The spaCy-based wrappers are primarily contained in the following:
|
@yinxiangshi I got |
@yinxiangshit I found this, and am digging in... https://spacy.io/usage/v3#features-training |
Is your feature request related to a problem? Please describe.
I want to use spaCy v3 to get transformers models. I want to use snorkel to do text extraction by giving it examples created in spaCy's annotation format. Just like the spouse demo only why do in tensorflow what spaCy does out of the box?
Describe the solution you'd like
Bump requirements.txt entry to spaCy to 3.0 and test the system, then include support in the next release.
Describe alternatives you've considered
It's probably possible to generate the v3 annotation format in v2 then run spaCy v3 in a separate program.
Additional context
spaCy v3 is amazing! https://nightly.spacy.io/
The text was updated successfully, but these errors were encountered: