From 42a8c2b2217fba0c02c86cef771c1604c44a5993 Mon Sep 17 00:00:00 2001
From: Guido van Rossum <guido@python.org>
Date: Thu, 9 Aug 2001 20:25:58 +0000
Subject: [PATCH] Add resolution of __new__ story sequel.

---
 PLAN.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/PLAN.txt b/PLAN.txt
index a0d2bea8fb..23f48948c6 100644
--- a/PLAN.txt
+++ b/PLAN.txt
@@ -99,6 +99,10 @@ we try to use this for some, eh, interesting types such as tuples. ***
             def __new__(cls, *args):
                 "How do I call the default __new__ implementation???"
 
+    This was resolved nicely by putting object.__new__ back but not
+    inheriting __new__ from object when the subtype is a built-in or
+    extension type.
+
 More -- I'm sure new issues will crop up as we go.
 
 
-- 
2.49.0