From: Guido van Rossum <guido@python.org>
Date: Wed, 8 Aug 2001 16:57:43 +0000 (+0000)
Subject: Added note to self about __new__ issue.
X-Git-Tag: v2.2a3~738
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0415620af924be8ae12d1017177724aa335c2847;p=python

Added note to self about __new__ issue.
---

diff --git a/PLAN.txt b/PLAN.txt
index d0530b4b19..3f2ae8b079 100644
--- a/PLAN.txt
+++ b/PLAN.txt
@@ -89,6 +89,15 @@ overridable, as metamethod mro().  I believe that closes this topic
 for now.  I expect that some warts will only be really debugged when
 we try to use this for some, eh, interesting types such as tuples. ***
 
+    There was a sequel to the __new__ story (see checkins).  There
+    still is a problem: object.__new__ now no longer exists, because
+    it was inherited by certain extension types that could break.  But
+    now when I write
+
+        class C(object):
+            def __new__(cls, *args):
+                "How do I call the default __new__ implementation???"
+
 More -- I'm sure new issues will crop up as we go.