homepage

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 rhettinger
Recipients abusalimov, gvanrossum, rhettinger, xtreak
Date 2018年09月28日.18:17:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538158656.13.0.545547206417.issue21919@psf.upfronthosting.co.za>
In-reply-to
Content
> I am adding Raymond as part of triaging who might have a better explanation about this. 
Guido, is this something we care about? There is value in checking for metaclass conflicts when a class is created (to catch plausible mistakes and to assure that the right __new__() and __init__() methods run). But post-creation, it's unclear whether there is value in rerunning checks and whether its even possible to know how other base classes might have affected the class creation.
Do this go in the "consenting adults" category (in the same way that we allow the __class__ attribute to be changed on instances without trying to verify whether it makes sense)?
History
Date User Action Args
2018年09月28日 18:17:36rhettingersetrecipients: + rhettinger, gvanrossum, abusalimov, xtreak
2018年09月28日 18:17:36rhettingersetmessageid: <1538158656.13.0.545547206417.issue21919@psf.upfronthosting.co.za>
2018年09月28日 18:17:36rhettingerlinkissue21919 messages
2018年09月28日 18:17:36rhettingercreate

AltStyle によって変換されたページ (->オリジナル) /