On 13 July 2013 16:05, Donald Stufft <don...@stufft.io> wrote: > > On Jul 13, 2013, at 1:31 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > > I'm currently leaning towards offering both, as we're going to need a tool > for bootstrapping source builds, but the simplest way to bootstrap pip for > Windows and Mac OS X users is to just *bundle a copy with the binary > installers*. So long as the bundled copy looks *exactly* the way it would > if installed later (so it can update itself), then we avoid the problem of > coupling the pip update cycles to the standard library feature release > cycle. The bundled version can be updated to the latest available versions > when we do a Python maintenance release. > > > We could simply check it into the site-packages inside the CPython source > tree could we not? *Not* providing a bootstrap script and merely checking > it into the default site-packages means it's available for everyone. No > matter how python installed. >
Source code that isn't maintained through bugs.python.org isn't getting checked into the CPython repo - see PEP 360. Getting the latest released version of something from PyPI is a different story, though. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
