This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: improve tracing performance with f_trace set to Py_None
Type: enhancement Stage: patch review
Components: Library (Lib) Versions: Python 3.6
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, serhiy.storchaka, xdegaye
Priority: normal Keywords: patch

Created on 2016-06-04 16:27 by xdegaye, last changed 2022-04-11 14:58 by admin.

Pull Requests
URL Status Linked Edit
PR 16157 closed nanjekyejoannah, 2019-09-15 13:23
Messages (1)
msg267262 - (view) Author: Xavier de Gaye (xdegaye) * (Python triager) Date: 2016-06-04 16:27
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.
Date User Action Args
2022-04-11 14:58:32adminsetgithub: 71405
2019-09-15 13:23:40nanjekyejoannahsetkeywords: + patch
stage: needs patch -> patch review
pull_requests: + pull_request15767
2016-06-04 17:35:52serhiy.storchakasetnosy: + serhiy.storchaka
2016-06-04 17:35:47serhiy.storchakasetstage: needs patch
2016-06-04 16:27:47xdegayecreate