Author CuriousLearner
Recipients CuriousLearner, Eric.Wieser, Rodolpho.Eckhardt, belopolsky, brian.curtin, eric.araujo, georg.brandl, henriquebastos, ncoghlan, robcliffe, ron_adam, terry.reedy
Date 2018-07-23.18:42:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

My perception with all the discussion and WIP patch is that we can ideally limit the no. of subclasses shown only for object, and not for any other class.

>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

I agree with this. I would propose to only limit to 4 classes for subclasses of `object` and for everything else displaying all the subclasses. We can optionally display the message to call `cls.__subclasses()` in the case when `help(object)` is called.

How does it sound?
Date User Action Args
2018-07-23 18:42:31CuriousLearnersetrecipients: + CuriousLearner, georg.brandl, terry.reedy, ncoghlan, belopolsky, ron_adam, eric.araujo, brian.curtin, robcliffe, henriquebastos, Rodolpho.Eckhardt, Eric.Wieser
2018-07-23 18:42:31CuriousLearnersetmessageid: <>
2018-07-23 18:42:31CuriousLearnerlinkissue8525 messages
2018-07-23 18:42:31CuriousLearnercreate