+1 for the '.' proposal, where (to verify my understanding):
- '.' indicates "import from the current package", '..' means "import
from the package of my package", and so forth,
- imports where the package part lacks a leading '.' are absolute, ie
from the top level of the path.
-1 for the '...' proposal, where '...' means a search from the current
package up to the most superior containing package (which is
actually a virtual package that entails the entire path).
Ie, i am for absolute being the default and explicit-relative being
available, and against ambiguous relative aka scanning the hierarchy.
(I might be convinced otherwise about the scanning deal, but i think
the more deterministic we can make imports, while still keeping them
flexible enough to do what people need, the better.)
I also like your proposal for a "no ambiguous imports" flag
from __future__ import absolute_import
Ken
klm at zope.com
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