Ok, so neither Python 2.7 nor Python 3.x’s ensure pip command will install a ``pip`` binary by default without a flag. That's fine with me, just wanted to make sure it made sense for Python 2.x. Thanks!
On Oct 3, 2014, at 8:31 PM, Guido van Rossum firstname.lastname@example.org wrote:
That is copying the (alt)install targets of Python's own Makefile, and I think those are exactly right.
On Oct 3, 2014 3:07 PM, "Donald Stufft" <email@example.com mailto:firstname.lastname@example.org> wrote: I'm working on the backport of ensurepip to Python 2.7, and I realized that I'm not sure which commands to install. Right now by default pip (outside of the context of ensurepip) will install pip, pip2, and pip2.7 if installed in Python 2.7. In Python 3's ensurepip we modified it so that it would install pip3, and pip3.4, but *not* pip if it was an "install", and only pip3.4 if it was an "alt install".
My question is, does this behavior make sense for ensurepip in 2.7? Or should it also install the "pip" command if it is an "install"?
Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
Python-Dev mailing list Python-Dev@python.org mailto:Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org https://mail.python.org/mailman/options/python-dev/guido%40python.org
--- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA