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.

Author scoder
Recipients Mark.Shannon, hroncok, petr.viktorin, rhettinger, scoder, vstinner
Date 2021-05-11.18:16:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1620756970.56.0.177047034601.issue43760@roundup.psfhosted.org>
In-reply-to
Content
For the same reason that motivated this ticket, I think the functions should be inline functions. They should also take the current thread-state as argument, because that's probably known on the caller side already.

I guess a macro would be fine, too. :)

Cython previously used "use_tracing" directly because it needs to implement the exact same tracing/profiling behaviour as CPython, regardless of who called a Cython implemented function (Cython or CPython).

Naming nit: Get/Is/UsesTracing?

Also, given that a common use case seems to be "make sure tracing is disabled, do something, enable tracing if it was enabled", I think DisableTracing() should return the previous state.
History
Date User Action Args
2021-05-11 18:16:10scodersetrecipients: + scoder, rhettinger, vstinner, petr.viktorin, Mark.Shannon, hroncok
2021-05-11 18:16:10scodersetmessageid: <1620756970.56.0.177047034601.issue43760@roundup.psfhosted.org>
2021-05-11 18:16:10scoderlinkissue43760 messages
2021-05-11 18:16:10scodercreate