On Tue, Apr 06, 2004, Barry Warsaw wrote: > On Tue, 2004-04-06 at 10:16, Aahz wrote: >> >> Rationale for Absolute Imports >> ============================== >> >> In Python 2.3 and earlier, if you're reading a module located inside a >> package, it is not clear whether :: >> >> import foo >> >> refers to a top-level module or to another module inside the package. >> As Python's library expands, more and more old modules suddenly shadow >> builtin modules by accident. > > As Python's library expands, more and more existing package internal > modules suddenly shadow standard library modules by accident. Done. Seems that the final remaining issue is the meaning of "." inside __init__.py -- does it refer to the current package or the parent? Guido, if you don't want to Pronounce, I'll post to c.l.py requesting feedback. -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ Why is this newsgroup different from all other newsgroups?
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