Message 380273 - Python tracker

Message380273

Author	mariocj89
Recipients	mariocj89
Date	2020-11-03.13:15:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1604409323.63.0.865948030488.issue42251@roundup.psfhosted.org>
In-reply-to

Content
When working in a C extension from a non-python created thread which calls PyGILState_Ensure as it later calls a Python callback on user code, I wished there was a way to set the trace function similar to what a native Python thread would do. We could just call sys.gettrace within the thread, but the application might have chosen to set threading.settrace differently. Same applies for threading.setprofile.

Content

When working in a C extension from a non-python created thread which calls PyGILState_Ensure as it later calls a Python callback on user code, I wished there was a way to set the trace function similar to what a native Python thread would do.

We could just call sys.gettrace within the thread, but the application might have chosen to set threading.settrace differently.

Same applies for threading.setprofile.

History
Date	User	Action	Args
2020-11-03 13:15:23	mariocj89	set	recipients: + mariocj89
2020-11-03 13:15:23	mariocj89	set	messageid: <1604409323.63.0.865948030488.issue42251@roundup.psfhosted.org>
2020-11-03 13:15:23	mariocj89	link	issue42251 messages
2020-11-03 13:15:23	mariocj89	create