-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
latest spaCy tagger and parser returning unexpected results #535
Comments
Code's correct; I must've broken something --- thanks! |
Hm, correct on my Linux server in both 2.7 and 3.5. Trying on OSX — but, very curious. I don't yet see what could be wrong. |
Ah. One nice change in 1.0.1 is that the tokenizer is bundled by default. Are you sure you're executing a version of spaCy that has the data installed? There's a bug here though...It's loaded the parser and tagger, even though their models are empty! |
How strange. :( I did a full un- then re-install of spacy, downloaded the models, and checked that it loads as specified in the docs; that process gave the results originally posted. Repeating this process, however, appears to have done the trick. (See below.) I have no idea what went wrong the first time, since I confirmed in my terminal history that nothing was done differently. Technology! ¯_(ツ)_/¯
Think we can assign blame to the gremlins in my machine, and close the issue. |
That's creepy. Hope I didn't mess something weird up. The loading stuff is all new code, so I expect there might be new bugs. |
I am facing the exact same issue when using the latest model (macOSx). I did complete uninstall and re-install, and now I find that all pos_ are 'PUNCT'. Definitely weird. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
After downloading the latest version of spaCy and updating the models, I no longer get reasonable POS tagging or dependency parsing. Here's an example in Python 3.5 on macOS Sierra:
Is this no longer correct code for v1.0.1? If it is, do you have any ideas what's going wrong?
The text was updated successfully, but these errors were encountered: