-
Notifications
You must be signed in to change notification settings - Fork 221
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
Support spaCy 3.0 #303
Comments
Yes, please see #295. It is in progress, thanks! |
Appreciate the rapid response, thank you! Please feel free to close this issue if you feel it's duplicative. |
I'll leave it open until we merge the PR so that other people can find it easily :) |
Slightly premature closing. We've uploaded new models that are compatible with master (and spacy 3), but haven't quite done a release yet. If you need it urgently, you should be able to use master and the new models. Otherwise, we should be doing a release sometime in the next week or so. |
Thank you for the quick response and turnaround, appreciate it! |
Anxiously awaiting, as well. Thank you. |
Release released! |
Great, thank you for the rapid turnaround! |
spaCy was upgraded to 3.0 this week and it appears the current version of scispacy is incompatible. I see there is a spacy3 branch and #295 appears to be a WIP on the upgrade.
Looks like a big pull on the move to 3.0. Do you have an idea on the timeline for the upgrade? Thank you for putting this project out there!
Here is the stack using a Python 3.8 virtualenv with spacy 3.0.1 and en_core_sci_md 0.3.0 installed.
The text was updated successfully, but these errors were encountered: