On 9/18/06, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote: > > Armin Rigo wrote: > > > My (limited) understanding of the motivation for relative imports is > > that they are only here as a transitional feature. Fully-absolute > > imports are the official future. > > Guido does seem to have a dislike for relative imports, > but I don't really understand why. The usefulness of > being able to make a package self-contained and movable > to another place in the package hierarchy without hacking > it seems self-evident to me. It is more of how relative imports used to be inherent and thus have no clear way to delineate that an import was being done using a relative path compared to an absolute one. What's happening in Py3k? Will relative imports still > exist? Using the dot notation, yes they will exist in Py3K. -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060918/01e1a07e/attachment.htm
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