diff options
| author | Victor Stinner <victor.stinner@gmail.com> | 2013-12-13 10:08:56 (GMT) |
|---|---|---|
| committer | Victor Stinner <victor.stinner@gmail.com> | 2013-12-13 10:08:56 (GMT) |
| commit | 590cebe391fb2e199afe9b20ff67e360116a1266 (patch) | |
| tree | 4adb2f6536cb319f479fbb2de06644f2ca32326d /Misc | |
| parent | cb1c4c8c22e27f0f7a01e1bb5ad78a804cf17c07 (diff) | |
| download | cpython-590cebe391fb2e199afe9b20ff67e360116a1266.zip cpython-590cebe391fb2e199afe9b20ff67e360116a1266.tar.gz cpython-590cebe391fb2e199afe9b20ff67e360116a1266.tar.bz2 | |
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.
Diffstat (limited to 'Misc')
| -rw-r--r-- | Misc/NEWS | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -10,6 +10,10 @@ Release date: 2014-01-05 Core and Builtins ----------------- +- Issue #19787: PyThread_set_key_value() now always set the value. In Python + 3.3, the function did nothing if the key already exists (if the current value + is a non-NULL pointer). + - Issue #14432: Remove the thread state field from the frame structure. Fix a crash when a generator is created in a C thread that is destroyed while the generator is still used. The issue was that a generator contains a frame, and |