On 16 July 2013 20:28, Richard Oudkerk <shibturn at gmail.com> wrote: > On 16/07/2013 6:44am, Nick Coghlan wrote: >> >> Clarifying what constitutes an internal interface in a way that >> doesn't require renaming anything is a necessary prerequisite for >> bundling or bootstrapping the pip CLI in Python 3.4 (as pip exposes >> its internal implemetnation API as "import pip" rather than "import >> _pip" and renaming it would lead to a lot of pointless code churn). >> Without that concern, the topic never would have come up. > > > BTW, how does the use of __all__ effect things? Somewhere I got the idea > that if a module uses __all__ then anything not listed is internal. I take > it that is wrong? Gah, you're right. I did consider that, then forgot to include it in the proposed text. Rather than throwing more versions of the text at the list, I'll create a tracker issue and post a proposed patch for PEP 8. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
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