➜

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 ppperry
Recipients Vadim Pushtaev, eric.snow, ncoghlan, ppperry, serhiy.storchaka
Date 2018-08-09.17:52:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1533837148.77.0.56676864532.issue34362@psf.upfronthosting.co.za>
In-reply-to
Content 
issue5322, despite its confusing title, mentions this exact bug in one of the comments below. 

It looks like there is one bug in the logic for assigning `__new__`, which causes `__new__` and `tp_new` to point to different things, confusing the error-handling logic in `object.__new__` as well as causing creation of a type by calling it to work in cases where direct calls to __new__ fail.

There's no one bug report about that, however issue5322, issue25731 and some cases of issue34284 are all symptoms of the same root issue.
History
Date User Action Args
2018-08-09 17:52:28ppperrysetrecipients: + ppperry, ncoghlan, eric.snow, serhiy.storchaka, Vadim Pushtaev
2018-08-09 17:52:28ppperrysetmessageid: <1533837148.77.0.56676864532.issue34362@psf.upfronthosting.co.za>
2018-08-09 17:52:28ppperrylinkissue34362 messages
2018-08-09 17:52:28ppperrycreate