From: Serhiy Storchaka Date: Wed, 7 Dec 2016 09:27:55 +0000 (+0200) Subject: Issue #5322: Fixed setting __new__ to a PyCFunction inside Python code. X-Git-Tag: v3.7.0a1~1819 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1b58d8aafa5c4705deeb898027b33c4be7bc71e1;p=python Issue #5322: Fixed setting __new__ to a PyCFunction inside Python code. Original patch by Andreas Stührk. --- 1b58d8aafa5c4705deeb898027b33c4be7bc71e1 diff --cc Misc/NEWS index d076091481,c62543571a..1a874982e2 --- a/Misc/NEWS +++ b/Misc/NEWS @@@ -10,6 -10,24 +10,9 @@@ What's New in Python 3.7.0 alpha Core and Builtins ----------------- + - Issue #5322: Fixed setting __new__ to a PyCFunction inside Python code. + Original patch by Andreas Stührk. + -Library -------- - -- Issue #28847: dbm.dumb now supports reading read-only files and no longer - writes the index file when it is not changed. - - -What's New in Python 3.6.0 release candidate 1 -============================================== - -*Release date: 2016-12-06* - -Core and Builtins ------------------ - - Issue #23722: Rather than silently producing a class that doesn't support zero-argument ``super()`` in methods, failing to pass the new ``__classcell__`` namespace entry up to ``type.__new__`` now results in a