[issue12917] Make visiblename and allmethods functions public

2011-09-12 Thread Éric Araujo
Éric Araujo added the comment: A precision: > I think generic functions would be a nice way to do this. I meant: a nice way to experiment this *outside of the stdlib*. We don’t have official generic function yet, so I’ll wait to see if pprint gets rewritten and/or if we get a generic functio

[issue12917] Make visiblename and allmethods functions public

2011-09-12 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- resolution: -> rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue12917] Make visiblename and allmethods functions public

2011-09-12 Thread Éric Araujo
Éric Araujo added the comment: Copied from msg143857: > There are a lot of little internal routines in the standard library > that aren't sufficiently fit to be exposed (perhaps a little too > ad-hoc or special purpose, perhaps the API isn't sufficiently > general, perhaps the routines rely on

[issue12917] Make visiblename and allmethods functions public

2011-09-11 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue12917] Make visiblename and allmethods functions public

2011-09-06 Thread Éric Araujo
New submission from Éric Araujo : pydoc contains these two functions that could be used by third-party code to implement a custom dir function, write a documentation tool or other uses: visiblename and allmethods. We could make them public, in pydoc or inspect. -- components: Library