➜

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.

classification
Title: _PyEval_RequestCodeExtraIndex should return a globally valid index, not a ThreadState specific one
Type: behavior Stage:
Components: Interpreter Core Versions: Python 3.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: jeethu, jpe
Priority: normal Keywords:

Created on 2016-10-24 15:32 by jpe, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg279314 - (view) Author: John Ehresman (jpe) * Date: 2016-10-24 15:32 
The index returned by _PyEval_RequestCodeExtraIndex is currently specific to the current thread state.  This means that there will be problems if the index is used on another thread.  It would be possible to set things up in my code so that _PyEval_RequestCodeExtraIndex was called once per thread state but there would be a possibility of getting different indices on the different threads and data set on one thread passed to the wrong free function registered on a different thread.
History
Date User Action Args
2022-04-11 14:58:38adminsetgithub: 72707
2018-01-17 02:33:28jeethusetnosy: + jeethu
2016-10-24 15:32:25jpecreate