[New-bugs-announce] [issue27218] improve tracing performance with f_trace set to Py_None

Xavier de Gaye report at bugs.python.org
Sat Jun 4 12:27:47 EDT 2016

New submission from Xavier de Gaye:

When a trace function set by sys.settrace() returns None, tracing of the current scope should stop, but this feature is not implemented (issue 11992).
Currently f_trace is never set to Py_None.  Setting f_trace to Py_None in trace_trampoline() when the trace function returns Py_None provides a way to avoid the costly calls to maybe_call_line_trace() that are made for each line in this scope even though the trace function is not called. This idea was initiated in issue 20041.

components: Library (Lib)
messages: 267262
nosy: georg.brandl, xdegaye
priority: normal
severity: normal
status: open
title: improve tracing performance with f_trace set to Py_None
type: enhancement
versions: Python 3.6

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list