➜

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 memeplex
Recipients Hari.Krishna.Dara, amaury.forgeotdarc, aventurella, benjamin.peterson, borisompol, farcat, flox, glchapman, krzysiekj, kynan, lorph, lukasz.langa, memeplex, mwh
Date 2016-07-12.01:59:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468288774.44.0.671226097003.issue672115@psf.upfronthosting.co.za>
In-reply-to
Content 
I understand Michael's comment http://bugs.python.org/issue672115#msg14169 but I'm failing to see how it's directly related to this issue: as Michael himself said it's even relevant for the object-subclass-object hack or for any hierarchy whatsoever. Is the comment warning about the entire writable-bases idea? It feels to me like the behavior should be consistently extended or consistently banned, but currently some cases work, another cases don't, and there seems to be no clear rationale supporting this state of affairs. Am I wrong?
History
Date User Action Args
2016-07-12 01:59:34memeplexsetrecipients: + memeplex, mwh, glchapman, amaury.forgeotdarc, lorph, benjamin.peterson, farcat, flox, Hari.Krishna.Dara, lukasz.langa, kynan, aventurella, krzysiekj, borisompol
2016-07-12 01:59:34memeplexsetmessageid: <1468288774.44.0.671226097003.issue672115@psf.upfronthosting.co.za>
2016-07-12 01:59:34memeplexlinkissue672115 messages
2016-07-12 01:59:33memeplexcreate