[issue1021318] PyThreadState_Next not thread safe

STINNER Victor report at bugs.python.org
Fri Mar 13 09:46:53 EDT 2020

Previous message (by thread): [issue35370] Add _PyEval_SetTrace(tstate, func, arg) function
Next message (by thread): [issue39956] Numeric Literals vs string "1_1" on input int() or float() or literal_eval
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

STINNER Victor <vstinner at python.org> added the comment:

See also bpo-35370: "Add _PyEval_SetTrace(tstate, func, arg) function".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1021318>
_______________________________________

Previous message (by thread): [issue35370] Add _PyEval_SetTrace(tstate, func, arg) function
Next message (by thread): [issue39956] Numeric Literals vs string "1_1" on input int() or float() or literal_eval
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-bugs-list mailing list