[issue22295] Clarify available commands for package installation

Change by Ville Skyttä : -- nosy: +scop nosy_count: 4.0 -> 5.0 pull_requests: +29462 pull_request: https://github.com/python/cpython/pull/24003 ___ Python tracker ___

[issue22295] Clarify available commands for package installation

Roundup Robot added the comment: New changeset e8447da8791d by Nick Coghlan in branch '3.4': Issue #22295: Adopt 'python -m pip' as the preferred invocation http://hg.python.org/cpython/rev/e8447da8791d New changeset a969b42e6e2b by Nick Coghlan in branch 'default': Merge issue #22295 fix from

[issue22295] Clarify available commands for package installation

Nick Coghlan added the comment: Switched to python -m pip. To deal with python3 vs python parallel system installs, I made the assumption that folks are using virtual environments explicitly, rather than diving into the arcana associated with using pip in conjunction with a system Python

[issue22295] Clarify available commands for package installation

New submission from Nick Coghlan: https://docs.python.org/3/installing/index.html is too subtle in pointing out the command in a source build or system Python on POSIX is pip3 or pip3.4 rather than the unadorned pip. At least one example should show pip3, and it's likely worth having an

[issue22295] Clarify available commands for package installation

Donald Stufft added the comment: If you want to be completely unambiguous, python -m pip works as well. -- nosy: +dstufft ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22295 ___

[issue22295] Clarify available commands for package installation

Nick Coghlan added the comment: Yes, that came up on Twitter as well (where this conversation started). I think that's the best way to go - it's the only invocation that works *everywhere*, regardless of how your Python instance got installed. --