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 serhiy.storchaka
Recipients Ringding, Trundle, aronacher, benjamin.peterson, doko, gvanrossum, jdemeyer, larry, ned.deily, prologic, python-dev, sebastinas, serhiy.storchaka, thansen, vstinner
Date 2016-12-12.10:52:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481539952.52.0.0240789167185.issue5322@psf.upfronthosting.co.za>
In-reply-to
Content
Thank you Jeroen. It looks to me that all problems can be resolved by reordering base classes and making Cython not generating trivial __new__. But that is possible only in new Python version. In maintained versions we should keep the old behavior for backward compatibility even if it contradicts normal rules for method resolution and the behavior of Python classes. We should find other solution for making explicit __new__ assigning working.
History
Date User Action Args
2016-12-12 10:52:32serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, doko, vstinner, larry, sebastinas, benjamin.peterson, ned.deily, aronacher, prologic, Trundle, Ringding, python-dev, jdemeyer, thansen
2016-12-12 10:52:32serhiy.storchakasetmessageid: <1481539952.52.0.0240789167185.issue5322@psf.upfronthosting.co.za>
2016-12-12 10:52:32serhiy.storchakalinkissue5322 messages
2016-12-12 10:52:32serhiy.storchakacreate