From: Victor Stinner Date: Fri, 13 Dec 2013 11:15:31 +0000 (+0100) Subject: (Merge 3.3) Issue #19969: PyBytes_FromFormatV() now raises an OverflowError if X-Git-Tag: v3.4.0b2~235 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=507ac3a5910a5404013883ce45ad2f9cf0509b0e;p=python (Merge 3.3) Issue #19969: PyBytes_FromFormatV() now raises an OverflowError if "%c" argument is not in range [0; 255]. --- 507ac3a5910a5404013883ce45ad2f9cf0509b0e diff --cc Misc/NEWS index eca89cc7a5,a66834944d..f99a0d82f8 --- a/Misc/NEWS +++ b/Misc/NEWS @@@ -10,20 -10,14 +10,23 @@@ Release date: 2014-01-0 Core and Builtins ----------------- + - Issue #19969: PyBytes_FromFormatV() now raises an OverflowError if "%c" + argument is not in range [0; 255]. + -- Issue #14432: Generator now clears the borrowed reference to the thread - state. 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 the frame kept a reference to the Python state of the - destroyed C thread. The crash occurs when a trace function is setup. +- 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 + the frame kept a reference to the Python state of the destroyed C thread. The + crash occurs when a trace function is setup. + +- Issue #19576: PyGILState_Ensure() now initializes threads. At startup, Python + has no concrete GIL. If PyGILState_Ensure() is called from a new thread for + the first time and PyEval_InitThreads() was not called yet, a GIL needs to be + created. - Issue #17576: Deprecation warning emitted now when __int__() or __index__() return not int instance.