On Mon, Nov 6, 2017 at 5:06 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > On 6 November 2017 at 09:08, Chris Angelico <ros...@gmail.com> wrote: >> On Mon, Nov 6, 2017 at 9:29 AM, Barry Scott <ba...@barrys-emacs.org> wrote: >>> If this is a mechanism that python kitting has then you would be able to >>> bundle other packages like requests or six as well as typing, but because >>> you can use pip to override the one shipped a user can optionally keep >>> up with the latest versions. >> >> If this were to happen, I would be inclined to put these "bootstrap" >> modules into their own directory in sys.path, after the rest of the >> stdlib. Then someone who's paranoid about stdlib shadowing could put >> pip-installed modules after the bulk of the stdlib (thus preventing >> any third-party package from overriding "import random", for instance) >> but still update modules that are specifically intended for updating; >> plus it'd mean you can get a directory listing of that, and go grab >> all the "blessed by python.org as an extension of the stdlib" >> packages. > > When we say bundled, we mean bundled: the exact same bits you would > get from PyPI, installed the same way, and if you upgrade it system > wide, there's no trace of the one we bundled.
Oh, that's even better! :+1: ChrisA _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
