>  In theory, this table could be stored somewhere other than the code object, so that it doesn't actually get paged in or occupy cache unless tracing is on. 

As some of us mentioned before, that will hurt the ecosystem of profilers and debugger tools considerably

On Thu, 23 Jul 2020 at 18:08, Jim J. Jewett <jimjjewett@gmail.com> wrote:
In theory, this table could be stored somewhere other than the code object, so that it doesn't actually get paged in or occupy cache unless tracing is on.  Whether that saves enough to be worth the extra indirections when tracing is on, I have no intention of volunteering to measure.  I will note that in the past, taking out docstrings (not even just moving them to a dict of [code:docstring] -- just taking them out completely) has been considered worthwhile.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@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/HEXSSC35MFWFKFRK6TO4N5SBJDTZAZOS/
Code of Conduct: http://python.org/psf/codeofconduct/