Am 17.11.2010 22:16, schrieb Éric Araujo:
>> Excluding a builtin name from __all__ sounds like a perfectly sensible
>> idea, so even if it wasn't deliberate, I'd say it qualifies as
>> fortuitous :)
> 
> But then, a tool that looks into __all__ to find for example what
> objects to document will miss open.  I’d put open in __all__.

So it comes down again to what we'd like __all__ to mean foremost:
public API, or just a list for "import *"?

Georg

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to