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
Date 2013-11-16.11:59:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384603153.53.0.793395121902.issue19553@psf.upfronthosting.co.za>
In-reply-to
Content
For 8 in particular, I'm inclined to push that over to the pip side of the fence (as with the first 7 points). pip knows that ensurepip is involved (due to ENSUREPIP_OPTIONS being set in the environment), so it may be able to check if the unversioned scripts are missing and generate them appropriately in that case.

How do we want to proceed for the first beta? Given the integration timeline in the PEP (which doesn't require the shipped version of pip to be locked until just before beta 2), I'm inclined not to consider the additional quirks Ned found as blockers for beta 1, but we do need to get them fixed for beta 2.
History
Date User Action Args
2013-11-16 11:59:13ncoghlansetrecipients: + ncoghlan, loewis, larry, ned.deily, dstufft
2013-11-16 11:59:13ncoghlansetmessageid: <1384603153.53.0.793395121902.issue19553@psf.upfronthosting.co.za>
2013-11-16 11:59:13ncoghlanlinkissue19553 messages
2013-11-16 11:59:13ncoghlancreate