> > Because in the current situation the meaning of an import is > > ambiguous. > > What exactly is ambiguous about it? Looking at "import foo" you can't tell whether there's a module foo expected in the current package or in the top-level module namespace. --Guido van Rossum (home page: http://www.python.org/~guido/)
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