Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #11073
| Date | 2011-08-09 09:34 -0700 |
|---|---|
| From | Ethan Furman <ethan@stoneleaf.us> |
| Subject | __all__ |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2070.1312906708.1164.python-list@python.org> (permalink) |
Greetings! Does anyone know/recall the original purpose of __all__? I had thought it was primarily to specify what would be imported when `from ... import *` was executed, such as for tk; today, it seems it is also used to specify the API for the module, and so the help() subsystem will only provide details for those items found in __all__. The issue I'm having with this is that there are roughly a dozen items I would like to make available via the `import *` mechanism in my dbf module, and another dozen that, while part of the public API, don't need to be available via an `import *`. History lessons, as well as ideas, welcomed! ~Ethan~
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
__all__ Ethan Furman <ethan@stoneleaf.us> - 2011-08-09 09:34 -0700
Re: __all__ Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2011-08-10 02:57 +1000
Re: __all__ Ethan Furman <ethan@stoneleaf.us> - 2011-08-12 13:15 -0700
csiph-web