A few thoughts:
pip is likely already distributed along with whatever built-in Python versions are in Glitch. It’s possible the module resolution for one version of Python was expecting to find a particular version of
- Your system environment may have been reset, e.g., your terminal session ended, and your
PATH was subsequently reset. It’s a common mistake for folks to make transitive changes and forget to modify the
PATH environment variable based on those changes.
It’s likely the latter occurred or some combination of the two.
pip is very hard to deal with when there are multiple versions of Python installed because of the way module resolution works (or, rather, doesn’t work) in Python.
I just want to point out that your workflow is in no way flawed. You should be able to install
pip in virtual environments and that version should work.
EDIT: There’s also
pip3. I don’t know which version of Python you’re using but there might be a difference between the two if
pip isn’t symbolically linked to
pip3. Confusingly, I think Homebrew now distributes what it used to call
python@3 as just
python. The corresponding
pip may or may not be aliased similarly. I can’t recall.