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 pitrou
Recipients daniel.urban, eric.araujo, pitrou, rhettinger, sbt, serhiy.storchaka, thomas.chiroux, vstinner
Date 2017-04-08.15:32:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491665558.43.0.48008087473.issue16572@psf.upfronthosting.co.za>
In-reply-to
Content
Multi-inheritance is tricky to get right, both for the class being extended and the class extending it.  The APIs mentioned here were never designed for multiple inheritance and aren't supposed to support it.

Your use case would probably be better served by using composition rather than inheritance.  Speaking personally, I almost never subclass Thread, instead I make it an attribute of whatever class I'm writing.
History
Date User Action Args
2017-04-08 15:32:38pitrousetrecipients: + pitrou, rhettinger, vstinner, eric.araujo, daniel.urban, sbt, serhiy.storchaka, thomas.chiroux
2017-04-08 15:32:38pitrousetmessageid: <1491665558.43.0.48008087473.issue16572@psf.upfronthosting.co.za>
2017-04-08 15:32:38pitroulinkissue16572 messages
2017-04-08 15:32:38pitroucreate