[issue27218] improve tracing performance with f_trace set to Py_None

2019-09-15 Thread Joannah Nanjekye
Change by Joannah Nanjekye : -- keywords: +patch pull_requests: +15767 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/16157 ___ Python tracker

[issue27218] improve tracing performance with f_trace set to Py_None

2016-06-04 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue27218] improve tracing performance with f_trace set to Py_None

2016-06-04 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue27218] improve tracing performance with f_trace set to Py_None

2016-06-04 Thread Xavier de Gaye
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