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 ncoghlan
Recipients CuriousLearner, Eric.Wieser, Rodolpho.Eckhardt, belopolsky, brian.curtin, eric.araujo, georg.brandl, henriquebastos, ncoghlan, robcliffe, ron_adam, terry.reedy
Date 2018-07-24.10:47:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532429266.33.0.56676864532.issue8525@psf.upfronthosting.co.za>
In-reply-to
Content
I think the way modules display this information may actually provide a solid precedent that addresses the dynamic state problem I'm concerned about: filter the subclass list to only include subclasses that come from the same module as the object being displayed, and use the existing showtree/getclasstree interfaces to display the nested hierarchy nicely (the same way modules do).

Then the "... and NNN other subclasses in other modules" would only be appended when there was cross-module inheritance involved.
History
Date User Action Args
2018-07-24 10:47:46ncoghlansetrecipients: + ncoghlan, georg.brandl, terry.reedy, belopolsky, ron_adam, eric.araujo, brian.curtin, robcliffe, henriquebastos, Rodolpho.Eckhardt, Eric.Wieser, CuriousLearner
2018-07-24 10:47:46ncoghlansetmessageid: <1532429266.33.0.56676864532.issue8525@psf.upfronthosting.co.za>
2018-07-24 10:47:46ncoghlanlinkissue8525 messages
2018-07-24 10:47:46ncoghlancreate