Would it be possible to add a __file__ attribute? Victor
On Tue, Sep 28, 2021 at 2:47 PM Pablo Galindo Salgado <pablog...@gmail.com> wrote: > > > What is the annoyance? What is different between frozen and not frozen? > > One interesting consequence of what Eric mentioned (They have a different > loader and repr. Also, frozen modules do not > have __file__ set (and __path__ is always []).) is that frozen modules don't > have a `__file__` attribute IIRC and therefore > tracebacks won't include the source. > > > On Mon, 27 Sept 2021 at 22:31, Victor Stinner <vstin...@python.org> wrote: >> >> Hi Eric, >> >> Which stdlib modules are currently frozen? If I really want to hack >> site.py or os.py for whatever reason, I just have to use "python3 -X >> frozen_modules=off"? >> >> > 1. always default to "on" (the annoyance for contributors isn't big >> > enough?) >> >> What is the annoyance? What is different between frozen and not frozen? >> >> Victor >> >> On Mon, Sep 27, 2021 at 6:58 PM Eric Snow <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? >> > >> > -eric >> > >> > >> > [1] https://bugs.python.org/issue45020 >> > [2] FWIW, we may end up also freezing the modules imported for "python >> > -m ...", along with some other commonly used modules (like argparse). >> > That is a separate discussion. >> > _______________________________________________ >> > 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/4ESW3NNOX43DRFKLEW3IMDXDKPDMNRGR/ >> > Code of Conduct: http://python.org/psf/codeofconduct/ >> >> >> >> -- >> Night gathers, and now my watch begins. It shall not end until my death. >> _______________________________________________ >> 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/CLODS7B5Z3UEZTQ7QIALG2DWB4H37EWP/ >> Code of Conduct: http://python.org/psf/codeofconduct/ -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ 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/CRL7C7I2VHGI56TFJMK6U53LCKRRHDA3/ Code of Conduct: http://python.org/psf/codeofconduct/
