Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

switch to python3 -m pip #356

Closed
wants to merge 1 commit into from

Conversation

TheTechRobo
Copy link
Contributor

Using pip3 and pip is frowned upon.

@JustAnotherArchivist
Copy link
Owner

Amazing that someone spent the time to write all that text and still missed that minor-version commands like pip3.10, which fix their only technical argument about why python -m pip might be preferred, have been a thing since 2013 and existed in a slightly different form already in 2010 before pip even hit version 1.0...

Thanks, hadn't heard this one before, but pip is perfectly fine in my eyes.

@JustAnotherArchivist JustAnotherArchivist added the wontfix This will not be worked on label Jan 11, 2022
@TheTechRobo TheTechRobo deleted the patch-1 branch January 11, 2022 22:42
@JustAnotherArchivist JustAnotherArchivist added documentation and removed wontfix This will not be worked on labels Jan 12, 2022
@JustAnotherArchivist
Copy link
Owner

Read a bit more about this, and apparently the official intent is indeed to deprecate those commands at some point. Although the arguments still seem very poor to me; essentially, it boils down to 'what if the shebang in the pip command points to the wrong Python version‽', which can be fixed by using #!/usr/bin/env python3 (or the minor version or whatever) instead of hardcoding a path. (Not sure what typical installations of pip do there as I use pyenv on my systems, which handles this differently.) The other argument I found is 'what if you have multiple patch versions of the same minor version installed‽', but your system is already all kinds of messed up if you have that without proper isolation.

In any case, this was first raised in 2015, and there hasn't been any movement on it in years. Some relevant discussions: pypa/pip#3164 pypi/warehouse#1563

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants