seems to work thanks. That said, I would love to have PyThreadState_Get equivalent that would let me handle the NULL.
On Mon, Jan 18, 2016 at 9:31 PM, Maciej Fijalkowski <fij...@gmail.com> wrote: > Good point > > On Mon, Jan 18, 2016 at 9:25 PM, Victor Stinner > <victor.stin...@gmail.com> wrote: >> Hum, you can try to lie and define Py_BUILD_CORE? >> >> Victor >> >> 2016-01-18 21:18 GMT+01:00 Maciej Fijalkowski <fij...@gmail.com>: >>> Hi >>> >>> change in between 3.5.0 and 3.5.1 (hiding _PyThreadState_Current and >>> pyatomic.h) broke vmprof. The problem is that as a profile, vmprof can >>> really encounter _PyThreadState_Current being null, while crashing an >>> interpreter is a bit not ideal in this case. >>> >>> Any chance, a) _PyThreadState_Current 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@python.org >>> https://mail.python.org/mailman/listinfo/python-dev >>> Unsubscribe: >>> https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
