I think the
pip command you installed spaCy and Prodigy with is likely referring to a different installation from the one your
python.exe is referring to. This is a really common annoyance — it still happens to me a lot! I think this is true of all Python developers, unfortunately.
Try comparing the following:
python -c "import pip; print(pip.__file__)"
If they show different paths, you know that’s definitely what’s gone wrong. It’s possible you didn’t “activate” your environment correctly? It’s also possible that your execution paths aren’t correct. I find conda particularly pernicious in this respect — I still don’t really understand its behaviour. It seems if you don’t let it insert itself at the beginning of your execution path, it really doesn’t work at all.