This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients dstufft, larry, loewis, ncoghlan, ned.deily, tshepang
Date 2013-11-04.14:14:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383574474.62.0.277616494587.issue19406@psf.upfronthosting.co.za>
In-reply-to
Content
I'm OK with an unqualified "pip install --upgrade pip" retaining pip's current behaviour of always writing the unqualified script versions.

However, running "pip3 install --upgrade pip" would ideally leave the "pip" and "easy_install" scripts alone.

For "make altinstall" compatibility, we definitely need a "--altinstall" flag that only installs the fully qualified versions of pip and easy_install.

Finally, there needs to be some way to explicitly request the "pip3" style behaviour when running via -m so we can use it from ensurepip.
History
Date User Action Args
2013-11-04 14:14:34ncoghlansetrecipients: + ncoghlan, loewis, larry, ned.deily, tshepang, dstufft
2013-11-04 14:14:34ncoghlansetmessageid: <1383574474.62.0.277616494587.issue19406@psf.upfronthosting.co.za>
2013-11-04 14:14:34ncoghlanlinkissue19406 messages
2013-11-04 14:14:34ncoghlancreate