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 Eric.Wieser
Recipients CuriousLearner, Eric.Wieser, Rodolpho.Eckhardt, belopolsky, brian.curtin, eric.araujo, georg.brandl, henriquebastos, ncoghlan, robcliffe, ron_adam, terry.reedy
Date 2018-07-23.15:49:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532360992.82.0.56676864532.issue8525@psf.upfronthosting.co.za>
In-reply-to
Content
> I get the following results for builtin objects that have defined subclasses

From that list, the only unhelpful ones with > 4 items, in my opinion, appear to be `object`, since that just tells you every type that exists, and `tuple`, because that lists every single namedtuple.

> So it is USEFUL to know ALL subclasses of a given Exception class

I agree with this - most of the value here comes from showing the full set of exceptions. If we don't do that, we should probably point the user to calling `cls.__subclasses__()` so they can inspect the full list
History
Date User Action Args
2018-07-23 15:49:52Eric.Wiesersetrecipients: + Eric.Wieser, georg.brandl, terry.reedy, ncoghlan, belopolsky, ron_adam, eric.araujo, brian.curtin, robcliffe, henriquebastos, Rodolpho.Eckhardt, CuriousLearner
2018-07-23 15:49:52Eric.Wiesersetmessageid: <1532360992.82.0.56676864532.issue8525@psf.upfronthosting.co.za>
2018-07-23 15:49:52Eric.Wieserlinkissue8525 messages
2018-07-23 15:49:52Eric.Wiesercreate