On 20 July 2013 13:52, Marcus Smith <qwc...@gmail.com> wrote: > >> >> Folks are aware that get-pip.py includes an entire pip installation griped >> inside of it right? >> >> So if we ship get-pip.py we're shipping pip, which we'll then use to >> install pip over the network >> … instead of just shipping pip. > > > yes, it has pip in it. I mentioned it as something to improve for the > present, not ship. that would be odd
Actually, the main thing that made me realised that bundling pip with the installer for something else was a potentially flawed notion was that it would mean we'd be inflicting on *ourselves* exactly the same problem that already exists on Linux: two different file management tools (PEP 376 installers and the system package manager) fighting over the same Python installation. It wouldn't be as severe (since it would only affect one project), but it's still a potentially ugly mess. By contrast, the explicit bootstrap (whether using the current get-pip.py structure or a zip archive with a __main__.py file and whether executed at install time or later) ensures that the site-packages for that particular Python installation remains under the control of the PEP 376 installers (including pip). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
