hi @ami1902!
That's definitely a bit strange. I suspect something happened during the installation. It's hard to debug without more information.
A few questions:
- Was this a new install on that machine? Have you been able to install it on the machine before or is this the first time you've tried on this machine?
- Did you install Prodigy with a venv?
- Can you provide your versions of Prodigy and Python, and OS? You can do this from the output of
python -m prodigy stats
. Especially your version of Python may be of issue. - How did you install Prodigy? A wheel file, through
pip
, orconda
? - Can you try running
python3 -m prodigy ...
? I don't suspect this will be it since you can runpython -m prodigy stats
but sometimes aliases can be a bit weird. Related too, did you make try to install usingpip3
instead ofpip
too? - Could you try to install Prodigy into a fresh
venv
and make sure to have updatedpip install
beforehand (that is, runpython3 -m pip install --upgrade pip
before setting up thevenv
and installing Prodigy)?
If none of these things help, let us know and feel free to provide any additional information you think could help.