On 7 January 2015 at 00:12, Antoine Pitrou <solipsis at pitrou.net> wrote: > On Tue, 6 Jan 2015 23:56:30 +1000 > Nick Coghlan <ncoghlan at gmail.com> wrote: >> "pip" is problematic on Linux as well (due to the pip/pip3 split at >> the system level). Hence this section in the stdlib docs: >> https://docs.python.org/3/installing/#work-with-multiple-versions-of-python-installed-in-parallel > > Why doesn't it recommend "pip3.4", etc. instead? Am I missing something > about it? Those assume a pip-binary-per-Python-implementation model which isn't a valid assumption once Jython, PyPy, etc come into consideration. Indirecting through the Python implementation name helps ensure compatibility with a wider range of scenarios. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4