Roundup Robot added the comment:
New changeset 5d078b0bae75 by Victor Stinner in branch 'default':
Issue #19787: PyThread_set_key_value() now always set the value
http://hg.python.org/cpython/rev/5d078b0bae75
--
___
Python tracker
Changes by STINNER Victor victor.stin...@gmail.com:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19787
___
Changes by STINNER Victor victor.stin...@gmail.com:
--
title: tracemalloc: set_reentrant() should not have to call
PyThread_delete_key() - Fix PyThread_set_key_value() strange behaviour
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
Oh, my change on PyThread_set_key_value() has an unexpected effect on
_testcapi.run_in_subinterp(): it now fixes the Python thread state.
Py_NewInterpreter() creates a second Python thread state for the current
thread, but PyThread_set_key_value() ignored the
STINNER Victor added the comment:
My commit broke test_capi, so I revert it. Here is the commit as a patch.
The impact on subinterpreters is more complex than what I expected. A decision
should be take on what to do: mimic behaviour of Python 3.3 for subinterpreters
(don't replace the Python
