[issue8525] Display exceptions' subclasses in help()

Serhiy Storchaka added the comment: This caused a regression. See issue35614 for details. -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue8525] Display exceptions' subclasses in help()

Nick Coghlan added the comment: I've merged the version that displays up to 4 builtin subclasses in a flat list when help() is called on a type. Thanks for the patch Sanyam, and for the comments and suggestions everyone else. While I'm closing out this feature request as implemented, if

[issue8525] Display exceptions' subclasses in help()

Nick Coghlan added the comment: New changeset a323cdcb33c8c856e5668acfb2c67ab5198672c4 by Nick Coghlan (Sanyam Khurana) in branch 'master': bpo-8525: help() on a type now shows builtin subclasses (GH-5066) https://github.com/python/cpython/commit/a323cdcb33c8c856e5668acfb2c67ab5198672c4

[issue8525] Display exceptions' subclasses in help()

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue8525] Display exceptions' subclasses in help()

Nick Coghlan added the comment: 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

[issue8525] Display exceptions' subclasses in help()

Nick Coghlan added the comment: This is a UX problem folks: dynamic unbounded lists are inherently problematic in a line based information display. For methods on a class, there's the natural constraint that broad class APIs are a problem for a variety of reasons, but there's no such design

[issue8525] Display exceptions' subclasses in help()

Sanyam Khurana added the comment: Hi, 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`,

[issue8525] Display exceptions' subclasses in help()

Eric Wieser added the comment: > 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

[issue8525] Display exceptions' subclasses in help()

Rob Cliffe added the comment: On 14/07/2018 13:44, Nick Coghlan wrote: > Nick Coghlan added the comment: > > Reviewing the builtins in 3.7, I get the following results for builtin > objects that have defined subclasses immediately after interpreter startup: > > = for name,

[issue8525] Display exceptions' subclasses in help()

Nick Coghlan added the comment: Reviewing the builtins in 3.7, I get the following results for builtin objects that have defined subclasses immediately after interpreter startup: = >>> for name, obj in vars(builtins).items(): ... if isinstance(obj, type) and name in str(obj):

[issue8525] Display exceptions' subclasses in help()

Change by ppperry : -- title: Display exception's subclasses in help() -> Display exceptions' subclasses in help() ___ Python tracker