> 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,
I think this example should be in the PEP.
___
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
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
On 22Jul2020 1319, Mark Shannon wrote:
On 21/07/2020 9:46 pm, Gregory P. Smith wrote:
Q: Why can't we have the information about the entire span of lines
rather than consider a definition to be a "line"?
Pretty much every profiler, coverage tool, and debugger ever expects
lines to be
On 7/20/20 10:30 AM, Huang, Yang wrote:
>
> Hi, all
>
> There is a request to run python in a Linux-based embedded resource
> constrained system with sqlite3 support.
>
> So many features are not required, like posixmodule, signalmodule, hashtable
> ...
> But seems there are some dependencies
