Pip not responding to pyenv

[Shlok Sinha]

Hello 

The heading is pretty explanatory. I had started to use pyenv, but unfortunately, pip did not take that very well. I had set the global version to 3.8, such that my modules wouldn't face any compatibility issues. But pip wasn't still installing the packages, it stuck to the old 2.7 while the global version on the system had transformed to 3.8. Moreover, after I pipelined the two paths of 3.8 and 2.7 together after removing pyenv, pip then went back to its original directory (which is the global directory), and yes, continued to install under 2.7.

What my understanding is pip is configured with the version, not something independent, or the machine can't change its dependency. I was thinking maybe we could modify this a bit. While pip installs itself along with a python version, it can choose to be independent to the pre-existing versions in the systems, while still modifying and installing packages. I will be raising the issue on GitHub, but I think this forum is a good place to start a discussion.

cheers

Shlok

[Brett Cannon]

The easiest solution to this is to run pip via `python -m pip`. That way it is directly ties to the Python you use to execute it.

--
You received this message because you are subscribed to the Google Groups "pypa-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pypa-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pypa-dev/8eb43943-3887-4905-97e9-57627f8e6c8f%40googlegroups.com.