SPACY IMPORT ERROR!

How to reproduce the problem

“I’ve tried updating new versions of thinc and spacy as directed from previous issue posts.” Its flagging a import error.

# copy-paste the error message here

---

ImportError Traceback (most recent call last) <ipython-input-8-cb604e7f192b> in <module> 1 import pandas as pd 2 import string ----> 3 import spacy 4 from collections import Counter 5 from spacy.lang.en import English

~/opt/anaconda3/lib/python3.7/site-packages/spacy/init.py in <module> 8 9 # These are imported as part of the API —> 10 from thinc.api import prefer_gpu, require_gpu # noqa: F401 11 from thinc.api import Config 12

ImportError: cannot import name ‘prefer_gpu’ from ‘thinc.api’ (/Users/lexroverts/opt/anaconda3/lib/python3.7/site-packages/thinc/api.py)

Your Environment

• Operating System:IOS Mac
• Python Version Used: 3.7.6
• spaCy Version Used: 2.1.8
• Environment Information:

I need help trying to get spacy to work again on Jupiter notebooks.

[adrianeboyd]

pip lets you update packages even if this might cause conflicts with other currently installed packages. Notice the warnings at the bottom of the install message that show which packages are incompatible. Updating thinc independently from spacy can lead to mismatches. (In general it’s easier for us to help if the errors are pasted as text in a code block instead of as images, thanks!)

You may be able to fix your current virtual environment with pip install spacy==2.3.2. You also don’t want to have spacy and spacy-nightly installed in the same environment, so please uninstall with pip uninstall spacy-nightly. (Unless you want the prerelease version, then uninstall spacy and follow install instructions here: https://nightly.spacy.io/usage)

If that doesn’t work, we’d recommend starting with a new virtual environment and just installing spacy (pip install spacy, optionally with the stable version you’d like), which will pull in the correct versions of all the dependencies.

[github-actions[bot]]

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.