This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients james, larry, ncoghlan, yselivanov
Date 2015-04-13.16:49:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428943763.85.0.759427173291.issue23934@psf.upfronthosting.co.za>
In-reply-to
Content
James Powell is currently looking into this at the PyCon sprints.

The key problem appears to be the check that assumes "obj.__init__ is object.__init__" indicates that there's no user defined init or new method, when in fact a builtin or extension type that only overrides __new__ would also pass that check (since the earlier check for __new__ returns None if the method implementation isn't a pure Python callable)
History
Date User Action Args
2015-04-13 16:49:23ncoghlansetrecipients: + ncoghlan, larry, yselivanov, james
2015-04-13 16:49:23ncoghlansetmessageid: <1428943763.85.0.759427173291.issue23934@psf.upfronthosting.co.za>
2015-04-13 16:49:23ncoghlanlinkissue23934 messages
2015-04-13 16:49:23ncoghlancreate