-
-
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
Import Error with version 1.6.0 #855
Comments
Most of the time this sort of error comes down to the
And
To check that when you do If problems persist, the more manual process --- that therefore gives you more control --- is to clone the repository and compile the code using |
Just in case I created a new one with everything
I then proceeded to follow your steps and as far as I can tell it seemed to be alright. Building took a long time and there were a lot of outputs. Cannot really print it here. Unfortunately in the end I still get the same error. Here is the full list of packages that were installed
|
The |
I'm facing the same problem on MacOS Sierra with a new Miniconda installation. My error message is a tad different though and might be more helpful:
Ending in:
I have positively no clue where the |
Thanks @rolando installing with conda-forge solves the problem. Still don't know what's happening exactly. conda-forge installs these
and pip installs
It's a spot the difference game. In both cases I removed the spacy env and recreated it with Hope this helps. P.S.: In case you're wondering, I created a new account on the server just in case. That's why the user was alexis and now it's glitch |
Thanks for updating 🎉 |
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. |
Created a new env with conda
conda create -n spacy python=3.5 ipython
and then install spacy (1.6.0) with pip (conda still has version 0.101.0)
pip install spacy
But I still get this error.
There is a similar issue here explosion/sense2vec#19 but that solution did not help.
Note, I don't have that problem on MacOS Sierra.
Environment
The text was updated successfully, but these errors were encountered: