[Distutils] Expectations on how pip needs to change for Python 3.4

[Paul Moore]

On 13 July 2013 18:51, Donald Stufft <donald at stufft.io> wrote:

>
> On Jul 13, 2013, at 12:59 PM, Brett Cannon <brett at python.org> wrote:
>
> Could we just start to move away from an executable script and start
> promoting rather aggressively -m instead? It truly solves this problem and
> since the results are tied to the Python executable used (i.e. where
> something gets installed) it disambiguates what Python binary pip is going
> to work with (something I have trouble with thanks to Python 2 and 3 both
> being installed and each with their own pip installation). I realize older
> Python versions can't do this (I believe 2.6 and older can't for packages)
> but at least in the situation we are discussing here of bundling pip it's
> not an issue.
>
>
> Also looking at what already ships with Python.
>
> idle, idle2, idle2.7
> smtpd.py, smtpd2.py, smptd2.7.py
> pydoc, pydoc2, pydoc2.7
> 2to3, 2to3-2, 2to3-2.7
>
> This is also the convention anywhere someone does versioned scripts in a
> Python package in the ecosystem. PEP439 is there to streamline the process
> so that python dependencies are much easier to install and there's a
> smaller barrier to "entry" so that projects like Django can give simple
> instructions for dependencies instead of needing to opt not to have
> dependencies or have to give instructions on how to install the installer.
>

None of these commands work at the command line in a base Python install on
Windows. They are all obscure enough that nobody cares (or they are GUI
apps that have a start menu entry provided, i.e. Idle) - that won't be the
case for pip.

Paul.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20130713/ad4846de/attachment.html>