[Python-Dev] _PyThreadState_Current (original) (raw)
Victor Stinner victor.stinner at gmail.com
Tue Jan 19 07:32:39 EST 2016
- Previous message (by thread): [Python-Dev] _PyThreadState_Current
- Next message (by thread): [Python-Dev] Reference cycle on the module dict (globals())
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Since it's a regression introduced in Python 3.5.1, I propose to introduce a new private function _PyThreadState_FastGet() to reintroduce the feature: https://bugs.python.org/issue26154
Using afunction instead of using directly the variable hides how atomic variables are implemented and so avoid compiler issues.
Victor
2016-01-18 21:18 GMT+01:00 Maciej Fijalkowski <fijall at gmail.com>:
Hi
change in between 3.5.0 and 3.5.1 (hiding PyThreadStateCurrent and pyatomic.h) broke vmprof. The problem is that as a profile, vmprof can really encounter PyThreadStateCurrent being null, while crashing an interpreter is a bit not ideal in this case. Any chance, a) PyThreadStateCurrent can be restored in visibility? b) can I get a better API to get it in case it can be NULL, but also in 3.5 (since it works in 3.5.0 and breaks in 3.5.1) Cheers, fijal
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com
- Previous message (by thread): [Python-Dev] _PyThreadState_Current
- Next message (by thread): [Python-Dev] Reference cycle on the module dict (globals())
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]