➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: __all__ as determiner of a module's api
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: rhettinger Nosy List: pobrien, rhettinger
Priority: normal Keywords:

Created on 2002-10-30 14:20 by pobrien, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Messages (2)
msg13003 - (view) Author: Patrick K. O'Brien (pobrien) Date: 2002-10-30 14:20 
__all__ as a determiner of a module's api needs to be 
more fully documented. The only references I found were 
at http://www.python.org/doc/current/ref/import.html and 
http://www.python.org/doc/essays/packages.html. I also 
think the various uses of __all__ might be worthy of a 
small PEP, since I can't find any supporting 
documentation for the use of __all__ as anything more 
than controlling import *, which to me is not exactly the 
same thing as defining the public api for a module. It 
could be, and if it is meant to be then tools, such as 
IDLE, Boa, PythonWin and PyCrust should take __all__ 
into account when displaying autocompletion lists for 
modules.
msg13004 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2003-01-06 12:57 
Logged In: YES 
user_id=80475

Fixed.
See Doc/ref/ref6.tex 1.59
History
Date User Action Args
2022-04-10 16:05:48adminsetgithub: 37388
2002-10-30 14:20:34pobriencreate