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 daniel.urban, eric.araujo, pitrou, rhettinger, sbt, serhiy.storchaka, thomas.chiroux, vstinner
Date 2017-04-09.06:05:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491717906.3.0.297727666845.issue16572@psf.upfronthosting.co.za>
In-reply-to
Content
I'm going to decline this suggestion.  Antoine is right that this is a can of worms best less closed.  Likewise, Richard pointed out that there is potential to break existing code.

FWIW, the existence of super() does not imply that all existing classes need to rewritten with super calls.   "Cooperative multiple inheritance" implies a certain degree of pre-planning for meaningful cooperation between the classes.  For generic threading that doesn't seem plausible.

Also note that the referenced super-considered-super article shows how to incorporate non-cooperative classes in the chain without requiring that the original class be modified.
History
Date User Action Args
2017-04-09 06:05:06rhettingersetrecipients: + rhettinger, pitrou, vstinner, eric.araujo, daniel.urban, sbt, serhiy.storchaka, thomas.chiroux
2017-04-09 06:05:06rhettingersetmessageid: <1491717906.3.0.297727666845.issue16572@psf.upfronthosting.co.za>
2017-04-09 06:05:06rhettingerlinkissue16572 messages
2017-04-09 06:05:05rhettingercreate