On 15 July 2013 00:28, Brett Cannon <brett@python.org> wrote:
On Sun, Jul 14, 2013 at 2:13 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:
Based on the recent discussions, I now plan to reject the pip bootstrapping-on-first-invocation approach described in PEP 439 in favour of a new PEP that proposes: [SNIP] * ensuring that, for Python 3.4, "python3" and "python3.4" are available for command line invocation of Python, even on Windows
Can I ask why this is part of the PEP?
Mostly because "pip3" makes no sense without it. If we *don't* bring Windows into conformance with the way other platforms handle parallel Python 2 and Python 3 installs, then the PEP should document an explicit rationale for not doing it (the py launcher doesn't count in that regard, since the real purpose of that is to handle shebang lines through file associations, with the direct command line usage as an added bonus). Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia