Hi @fsa, similar to the thread you linked, this may still be an environment problem. Here are some potential solutions:
- Ensure that the Python environment you're running is the same as where you execute Prodigy
First, I'd like to know if the Python you're running whenever you execute python is the same as the one when you run in your Prodigy environment. Sometimes it may be python3 or even python3.7. Ensure that Prodigy is installed in the same environment. You can type something like:
which python
Afterwards, open the REPL of that python environment and try importing spacy , prodigy or even wasabi.
The important thing is to ensure that your Python environment is the same as where you've installed Prodigy.
- Install and Run prodigy inside a virtual environment.
Another option is to install prodigy in a virtual environment and work within that. You can do something like:
python -m venv venv
source venv/bin/activate
Then install Prodigy inside that virtual environment (path/to/venv/bin/pip install prodigy...). So instead of using the "global" Python in your system, you will just use what's provided in your user directory (it's usually path/to/venv/bin/python3).
- Figure out where libpython is located in your system and set that in the
LD_LIBRARY_PATHenvironment variable.
Lastly, you can also try things like setting the LD_LIBRARY_PATH before running the command. For example:
# first, let's locate where libpython is
which libpython
From what I remember, it's usually in /usr/***/libpython.... Afterwards, you can export this directory to the LD_LIBRARY_PATH variable:
export LD_LIBRARY_PATH=<path/to/libpython>