Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!xlned.com!feeder5.xlned.com!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.016 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'from:addr:ethan': 0.09; 'from:addr:stoneleaf.us': 0.09; 'from:name:ethan furman': 0.09; 'message-id:@stoneleaf.us': 0.09; 'received:gator410.hostgator.com': 0.09; '~ethan~': 0.09; 'api': 0.09; '__all__.': 0.16; 'executed,': 0.16; 'received:72.11': 0.16; 'received:72.11.125': 0.16; 'received:72.11.125.166': 0.16; 'received:gateway13.websitewelcome.com': 0.16; 'seems': 0.20; 'mechanism': 0.21; 'primarily': 0.21; 'module,': 0.23; 'specify': 0.24; "i'm": 0.27; 'import': 0.28; 'imported': 0.30; 'does': 0.32; 'anyone': 0.32; 'there': 0.33; 'to:addr:python-list': 0.33; 'that,': 0.33; '...': 0.34; 'header:User-Agent:1': 0.34; 'issue': 0.36; 'another': 0.37; 'to:addr:python.org': 0.39; 'history': 0.40; 'received:websitewelcome.com': 0.64; 'details': 0.65; 'received:184': 0.67; 'roughly': 0.67; 'today,': 0.67; 'ideas,': 0.73; 'received:69.56': 0.73; 'dozen': 0.91; 'greetings!': 0.93 Date: Tue, 09 Aug 2011 09:34:23 -0700 From: Ethan Furman User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Python Subject: __all__ Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator410.hostgator.com X-AntiAbuse: Original Domain - python.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - stoneleaf.us X-BWhitelist: no X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: mail.admailinc.com ([192.168.10.136]) [72.11.125.166]:1760 X-Source-Auth: ethan+stoneleaf.us X-Email-Count: 2 X-Source-Cap: dG9idWs7dG9idWs7Z2F0b3I0MTAuaG9zdGdhdG9yLmNvbQ== X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 17 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1312906708 news.xs4all.nl 23952 [2001:888:2000:d::a6]:41575 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:11073 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~