From: Martin Panter Date: Sun, 31 Jan 2016 06:33:16 +0000 (+0000) Subject: Issue #4806: Merge * unpacking fix from 3.5 X-Git-Tag: v3.6.0a1~673 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=cca32995b35aa9c371459e19caaa003d1e761b8a;p=python Issue #4806: Merge * unpacking fix from 3.5 --- cca32995b35aa9c371459e19caaa003d1e761b8a diff --cc Misc/NEWS index 5ea810cd5a,11ce59a768..ee39f998c8 --- a/Misc/NEWS +++ b/Misc/NEWS @@@ -10,12 -10,20 +10,16 @@@ Release date: tb Core and Builtins ----------------- + - Issue #4806: Avoid masking the original TypeError exception when using star + (*) unpacking in function calls. Based on patch by Hagen Fürstenau and + Daniel Urban. + -- Issue #26154: Add a new private _PyThreadState_UncheckedGet() function to get - the current Python thread state, but don't issue a fatal error if it is NULL. - This new function must be used instead of accessing directly the - _PyThreadState_Current variable. The variable is no more exposed since - Python 3.5.1 to hide the exact implementation of atomic C types, to avoid - compiler issues. +- Issue #26146: Add a new kind of AST node: ``ast.Constant``. It can be used + by external AST optimizers, but the compiler does not emit directly such + node. -- Issue #26194: Deque.insert() gave odd results for bounded deques that had - reached their maximum size. Now, the insert will happen normally and then - any overflowing element will be truncated from the right side. +- Issue #18018: Import raises ImportError instead of SystemError if a relative + import is attempted without a known parent package. - Issue #25843: When compiling code, don't merge constants if they are equal but have a different types. For example, ``f1, f2 = lambda: 1, lambda: 1.0``