On 11/16/2010 10:16 AM, Alexander Belopolsky wrote: > What this thread has shown is that there is no consensus on what > public names are and what rules should be followed when changing names > that can be imported from a module. Nor is their any consensus on the use of __all__ in the stdlib, with opinion ranging from never to sometimes to always. I do not have any opinions on the particular solution adopted, but appreciate your persistence in pushing to *some* solution. It would be nice to add 'Cleanly separated public and private APIs' to the list of 3.x features. -- Terry Jan Reedy
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4