[Distutils] PEP453 - Explicit bootstrapping of pip in Python installations
qwcode at gmail.com
Fri Aug 30 18:12:56 CEST 2013
ok, got it. so, theoretically if the pip/setuptools relationship stays
what it is at the moment, get-pip would end up including a bundled
setuptools to fulfill the "Not all users will have network access to PyPI"
On Fri, Aug 30, 2013 at 9:07 AM, Donald Stufft <donald at stufft.io> wrote:
> On Aug 30, 2013, at 12:04 PM, Marcus Smith <qwcode at gmail.com> wrote:
> > There's no mention of setuptools.
> > I guess the handling of that dependency (or not handling it up front, if
> pip is refactored such that setuptools just becomes a dependency when
> building) is considered an implementation detail of get-pip?
> It's not mentioned by name but instead it's said:
> An additional module called ``getpip`` will be added to the standard
> whose purpose is to install pip and any of its dependencies into the
> appropriate location (most commonly site-packages).
> Setuptools would be the "and any of its dependencies". I want to make
> setuptools not depend on setuptools but I added that as an escape clause
> incase that proves to be hard to actually do. The PEP itself specifies only
> pip because I'm considering setuptools an implementation detail of pip (one
> that can be replaced eventually or removed from it's "special" status).
> Donald Stufft
> PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Distutils-SIG