Issue42251
➜
This issue tracker will soon become read-only and move to GitHub.
For a smoother transition, remember to
log in and link your GitHub username to your profile.
For more information,
see this post about the migration.
Created on 2020-11-03 13:15 by mariocj89, last changed 2020-11-04 09:28 by pablogsal. This issue is now closed.
| Pull Requests | |||
|---|---|---|---|
| URL | Status | Linked | Edit |
| PR 23125 | merged | mariocj89, 2020-11-03 13:18 | |
| Messages (2) | |||
|---|---|---|---|
| msg380273 - (view) | Author: Mario Corchero (mariocj89) * ![]() |
Date: 2020-11-03 13:15 | |
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. |
|||
| msg380312 - (view) | Author: Pablo Galindo Salgado (pablogsal) * ![]() |
Date: 2020-11-04 09:28 | |
New changeset 0001a1b69ecda47b0406daa88c2943877580bcae by Mario Corchero in branch 'master': bpo-42251: Add gettrace and getprofile to threading (GH-23125) https://github.com/python/cpython/commit/0001a1b69ecda47b0406daa88c2943877580bcae |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020-11-04 09:28:10 | pablogsal | set | nosy:
+ pablogsal messages: + msg380312 |
| 2020-11-04 09:27:57 | pablogsal | set | status: open -> closed resolution: fixed stage: patch review -> resolved |
| 2020-11-03 13:18:56 | mariocj89 | set | keywords:
+ patch stage: patch review pull_requests: + pull_request22041 |
| 2020-11-03 13:15:23 | mariocj89 | create | |

