- Bug #1683368: The object.__init__() and object.__new__() methods are
now stricter in rejecting excess arguments. The only time when
either allows excess arguments is when it is not overridden and the
other one is. For backwards compatibility, when both are
overridden, it is a deprecation warning (for now; maybe a Py3k
warning later).
When merging this into 3.0, the warnings should become errors.
Note: without the change to string.py, lots of spurious warnings happen.
What's going on there?
diff --git a/Misc/NEWS b/Misc/NEWS
index 064e01d..fdada8d 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -1,4 +1,4 @@
-+++++++++++
+__init+++++++++++
Python News
+++++++++++
@@ -17,6 +17,13 @@
- Remove unused file Python/fmod.c.
+- Bug #1683368: The object.__init__() and object.__new__() methods are
+ now stricter in rejecting excess arguments. The only time when
+ either allows excess arguments is when it is not overridden and the
+ other one is. For backwards compatibility, when both are
+ overridden, it is a deprecation warning (for now; maybe a Py3k
+ warning later).
+
- Patch #1675423: PyComplex_AsCComplex() now tries to convert an object
to complex using its __complex__() method before falling back to the
__float__() method. Therefore, the functions in the cmath module now