Docs: Use python -m pip install everywhere#13257
Conversation
Follows a similar recent Django ticket: > https://code.djangoproject.com/ticket/30367 Quoting from that ticket/PR: > Using ``python -m pip install foo`` makes sure the copy of > pip looked up and executed is the one installed for the > interpreter copy currently in use (be it a system-wide > or a virtualenv's). This is not technically needed in a virtualenv, but the idea here is consistency: pick a single option that works everywhere and be consistent about it.
BoboTiG
left a comment
BoboTiG
left a comment
There was a problem hiding this comment.
Thanks @bsolomon1124, I am +1 for those changes.
brettcannon
left a comment
brettcannon
left a comment
There was a problem hiding this comment.
Could you add a comment explaining that the
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Per comment from @brettcannon.
|
I have made the requested changes; please review again. |
|
Thanks for making the requested changes! @brettcannon: please review the changes made to this pull request. |
|
Thanks! |
…13257) This is to help prevent people from accidentally installing into the wrong Python interpreter if they are not aware of which Python interpreter `pip` points to.
…13257) This is to help prevent people from accidentally installing into the wrong Python interpreter if they are not aware of which Python interpreter `pip` points to.
5 participants
Follows a similar recent Django ticket:
Quoting from that ticket/PR:
This is not technically needed in a virtualenv, but the idea here is consistency: pick a single option that works everywhere and be consistent about it.