[issue7798] Make generally useful pydoc functions public

2011-09-11 Thread Raymond Hettinger
Raymond Hettinger added the comment: Resist the urge to fatten APIs until you're sure that: * they are needed * they are well developed (many internal utils fail this test) * they are worth the extra time it takes to learn what is in a module (adding rarely needed tools has the side-effect of o

[issue7798] Make generally useful pydoc functions public

2011-09-06 Thread Éric Araujo
Éric Araujo added the comment: I’ve looked hard at pydoc and opened distinct bug reports so that each piece of maybe-useful functionality can be discussed independently: #12918 New module for terminal utilities #12917 Make visiblename and allmethods functions public #12916 Add inspect.splitdoc

[issue7798] Make generally useful pydoc functions public

2011-03-08 Thread Terry J. Reedy
Terry J. Reedy added the comment: I have looked at the pydoc module. Everything except help() is intended to be private. The author says within the file that __all__, when present, defines public interface and uses that definition within help() to decide what to display. So I do not think an