-
Notifications
You must be signed in to change notification settings - Fork 478
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
Kernel dies on running doc = nlp(u"abc...xyz") #189
Comments
Hi!
Any work around would be great, thanks! |
kernel is dying on doc=nlp(u'I have a dog, and I love her.'). not with ._. functions. |
Okay, but either way - any luck solving the problem? |
Same problem here. |
@Viole-Grace @vikrant094 Try to downgrade spacy to 2.1.0.
That did the trick for me. |
Thanks. It worked. |
As a workaround for the incompatibility issue, you can indeed either downgrade spaCy to 2.1.0, or build neuralcoref from source if you want to use a more recent version of spaCy. We plan on keeping the releases of neuralcoref and spaCy more in-sync in the future. Merging this with Issue #197. |
As @fhopp mentioned his steps worked for me. But If you get an error like: |
@svlandeg solution (from source) also works. Following up on @kr-prince if you are on MAC OS and get the gcc error, you will likely need to download/update your MAC devtools. |
I'm using jupyter notebook on gcloud, with a venv for package installation. System image - Ubuntu 16.04
Steps to recreate the error :
pip3 install neuralcoref
and then
`import spacy
import neuralcoref
nlp = spacy.load('en')
neuralcoref.add_to_pipe(nlp)
doc = nlp(u'Deepika has a dog. She loves him. The movie star has always been fond of animals')
doc..coref_clusters
doc..coref_resolved
`
I get the following warning first :
and then, the jupyter kernel dies.
I have tried building from source, following the readme for --no-binary as well, still the same issue persists. Kernel dies.
Any insight as to why this is happening / how to change any code to make it work would be much appreciated.
Thanks!
The text was updated successfully, but these errors were encountered: