You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=Nonecreated_at=<Date2016-06-04.16:27:47.484>labels= ['type-feature', 'library']
title='improve tracing performance with f_trace set to Py_None'updated_at=<Date2019-09-15.13:23:40.914>user='https://github.com/xdegaye'
When a trace function set by sys.settrace() returns None, tracing of the current scope should stop, but this feature is not implemented (bpo-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 bpo-20041.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: