[Distutils] Current status of PEP 439 (pip boostrapping)

Paul Moore p.f.moore at gmail.com
Sat Jul 13 15:32:57 CEST 2013


On 13 July 2013 13:25, Nick Coghlan <ncoghlan at gmail.com> wrote:

> I think we need to flip the dependencies so that pip as the installer has
> all the essential code for installation from PyPI and then setuptools and
> distlib depend on that pip infrastructure. No need to add anything to the
> standard library prematurely when we can add it to pip instead.


Agreed, up to a point. What I've worked on in the past is things like
automated wheel/sdist installers for systems with no internet access at all
(distributions copied onto the PC via portable disk) or behind broken
proxies (Internet Explorer works to download files from the net, but
nothing else does). For those environments, the key to me is that I *only*
use stuff that is available in a stock Python build. Something like pyton
-m getpip *will not work*, so I have to roll my own means of bootstrapping.

Of course I could copy a pip sdist to the machine, unpack it and run python
setup.py install. More likely, I write bootstrap code in my script to do
that automatically.

It's a very specialised use case, certainly, and there are plenty of ways
around the issues, but I have seen "give up and just use VBScript./perl"
used as the fallback, as well, and that makes me sad...

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


More information about the Distutils-SIG mailing list