On Tue, 28 Sep 2021 10:51:53 +0200 Ronald Oussoren via Python-Dev <python-dev@python.org> wrote: > > On 28 Sep 2021, at 10:05, Antoine Pitrou <anto...@python.org> wrote: > > > > On Mon, 27 Sep 2021 10:51:43 -0600 > > Eric Snow <ericsnowcurren...@gmail.com > > <mailto:ericsnowcurren...@gmail.com>> wrote: > >> We've frozen most of the stdlib modules imported during "python -c > >> pass" [1][2], to make startup a bit faster. Import of those modules > >> is controlled by "-X frozen_modules=[on|off]". Currently it defaults > >> to "off" but we'd like to default to "on". The blocker is the impact > >> on contributors. I expect many will make changes to a stdlib module > >> and then puzzle over why those changes aren't getting used. That's an > >> annoyance we can avoid, which is the point of this thread. > >> > >> Possible solutions: > >> > >> 1. always default to "on" (the annoyance for contributors isn't big > >> enough?) > >> 2. default to "on" if it's a PGO build (and "off" otherwise) > >> 3. default to "on" unless running from the source tree > >> > >> Thoughts? > > > > My vote is on #3 to minimize contributor annoyance and > > eventual puzzlement. > > I agree, but… Most CPython tests are run while running from the source tree, > that means that there will have to be testrunner configurations that run with > “-X frozen_modules=on”.
Well, multiplying CI configurations is the price of adding options in general. Regards Antoine. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/R6C5XNYBV7LGUWRAL4X4OQDABRKQW42C/ Code of Conduct: http://python.org/psf/codeofconduct/
