Author pitrou
Recipients Arfrever, Trundle, barry, djc, eric.araujo, nadeem.vawda, ncoghlan, petri.lehtinen, pitrou, python-dev, rpointel, skrah
Date 2011-12-04.09:19:17
SpamBayes Score 4.2353e-11
Marked as misclassified No
Message-id <1322990045.3484.4.camel@localhost.localdomain>
In-reply-to <1322988839.3484.2.camel@localhost.localdomain>
Content
> > Is the following change in behavior caused by the fix for this issue?
> > 
> > $ python3.2 -c $'class A(IOError):\n  def __init__(self, arg): pass\nA(arg=1)'
> > $ python3.3 -c $'class A(IOError):\n  def __init__(self, arg): pass\nA(arg=1)'
> > Traceback (most recent call last):
> >   File "<string>", line 3, in <module>
> > TypeError: A does not take keyword arguments
> 
> It must be because IOError now has a significant __new__ method.
> I could change it to accept arbitrary arguments but I'm not sure that's
> the right solution.
> Another approach would be:
> - if IOError is instantiated, initialize stuff in IOError.__new__
> - otherwise, initialize stuff in IOError.__init__

To make things clearer, IOError.__new__ would detect if a subclass is
asked for, and then defer initialization until __init__ is called so
that argument checking is done in __init__.
History
Date User Action Args
2011-12-04 09:24:00pitrousetrecipients: + pitrou, barry, ncoghlan, nadeem.vawda, djc, eric.araujo, Arfrever, Trundle, skrah, python-dev, petri.lehtinen, rpointel
2011-12-04 09:19:17pitroulinkissue12555 messages
2011-12-04 09:19:17pitroucreate