On 1 October 2013 00:35, Skip Montanaro <s...@pobox.com> wrote: > Splitting into two pieces also means you can implement it for 3.4 > first and identify possible problems caused by preexisting pip > installs before deciding whether to add it to 2.7 and 3.3.
One of the key reasons for using the bootstrap mechanism rather than just bundling pip is so that the installers for maintenance releases won't have any more trouble with pre-existing installs of pip than pip itself does :) But yes, there are several advantages to splitting the PEP: - the Python 3.4 changes are non-controversial, so it makes sense to get them officially accepted - the Python 3.4 beta deadline is closer than the deadlines for the 3.3.3 and 2.7.6 maintenance releases - it allows the full extent of the changes proposed for backporting to be clear prior to the reconsideration of the separated PEP - a Windows installer for pip could be made available well in advance of the 3.3.3 and 2.7.6 maintenance releases - it allows a chance to see if a separate Windows installer for pip and documenting the bootstrapping instructions in the "Installing Python Modules" guide for older releases is sufficient to get new users over the "getting started with PyPI" barrier Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
