➜

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 jdemeyer
Recipients Ringding, Trundle, aronacher, benjamin.peterson, doko, gvanrossum, jdemeyer, larry, ned.deily, prologic, python-dev, sebastinas, serhiy.storchaka, thansen, vstinner
Date 2016-12-12.13:53:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481550789.83.0.768598248167.issue5322@psf.upfronthosting.co.za>
In-reply-to
Content 
Wouldn't it be possible to fix assignment of __new__ without breaking backwards compatibility (and then apply the same patch for all Python versions)? I have a feeling that breaking the auto-detection of tp_new is a new bug introduced by this patch and not a fundamental feature needed to fix assignment of __new__.
History
Date User Action Args
2016-12-12 13:53:09jdemeyersetrecipients: + jdemeyer, gvanrossum, doko, vstinner, larry, sebastinas, benjamin.peterson, ned.deily, aronacher, prologic, Trundle, Ringding, python-dev, serhiy.storchaka, thansen
2016-12-12 13:53:09jdemeyersetmessageid: <1481550789.83.0.768598248167.issue5322@psf.upfronthosting.co.za>
2016-12-12 13:53:09jdemeyerlinkissue5322 messages
2016-12-12 13:53:09jdemeyercreate