Added note to self about __new__ issue.

This commit is contained in:
Guido van Rossum 2001-08-08 16:57:43 +00:00
parent ff88556af6
commit 0415620af9
1 changed files with 9 additions and 0 deletions

View File

@ -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 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. *** 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. More -- I'm sure new issues will crop up as we go.