homepage

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.

classification
Title: improve tracing performance with f_trace set to Py_None
Type: enhancement Stage: patch review
Components: Library (Lib) Versions: Python 3.6
process
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.
History
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

AltStyle によって変換されたページ (->オリジナル) /