Antoine Pitrou <pit...@free.fr> added the comment: > 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__ What do you think? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12555> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
