Victor Stinner 590cebe391 Issue #19787: PyThread_set_key_value() now always set the value
In Python 3.3, PyThread_set_key_value() did nothing if the key already exists
(if the current value is a non-NULL pointer).

When _PyGILState_NoteThreadState() is called twice on the same thread with a
different Python thread state, it still keeps the old Python thread state to
keep the old behaviour. Replacing the Python thread state with the new state
introduces new bugs: see issues #10915 and #15751.
2013-12-13 11:08:56 +01:00
..
2013-12-06 20:12:51 -05:00
2013-07-22 22:08:17 -07:00
2013-07-27 02:41:03 +02:00
2013-10-31 01:20:58 -04:00
2013-03-20 00:39:41 -05:00
2013-11-22 09:05:39 -07:00
2012-10-05 01:04:27 +02:00
2013-09-26 22:21:41 -04:00