-
Notifications
You must be signed in to change notification settings - Fork 477
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
ValueError: cymem.cymem.Pool has the wrong size, try recompiling #102
Comments
I got the same error, the solution for me was to downgrade Spacy. Anything between |
That fixed it. 👍 Will leave the closure of the issue to library devs in case they want to address this in the next release? |
Worked for me with |
Works for me with |
same problem. But I can't downgrade spacy. Windows will fail to install because of the thinc and other wheel |
This is an upstream issue, see: explosion/spaCy#2852 Easiest solution is: |
If you are in Anaconda environment, you can use: |
I'm re-referencing these issues to each other since there is a version conflict right now and it's not possible to use Please take a look at this comment of mine: explosion/spaCy#2852 (comment) |
I've spent all evening looking through code for both Spacy and Neuralcoref but can't see where the problem lies. It seems there were almost identical bugs in Prodigy explosion/spaCy#2852 as referenced by @mertyildiran and there the fix was in Prodigy, and seemingly not Spacy and not the supporting libraries thinc and msgpack I can confirm that installing spacy==2.0.12 and msgpack==5.6.5 does work but it is not a good solution in the longer term. Has anybody managed to get Neuralcoref running at all in 2.0.18? |
All these issues should be fixed with the new release (NeuralCoref 4.0) and SpaCy 2.1+. |
Same problem. Python 3.7 on Mac
|
Same issue here as well |
i meet same problem,but there is no any solution |
On installing with the
en_coref_md
link I encountered this error.Putting it here just in case it reveals a bug somewhere which makes the next release better.
Curiously, on the same machine in another environment the library works fine.
Will update if this goes away due to some action of mine.
The text was updated successfully, but these errors were encountered: