> > Uh? Maybe you should have some coffee and then try again. > > Don't drink coffee, remember? ;-) Well, whatever you do take to improve your brain function. > > __path__ has nothing to do with relative import. When I say > > "import foo.bar" then bar is searched for in foo.__path__. __path__ > > defines which directories comprise the package contents, nothing more > > or less. > > Yeah, I know; I think that ``as`` combined with relative imports can > obviate most uses for ``__path__``, but I'm now dealing with a family > emergency, so I'm going to just drop it. 'as' has nothing to do with __path__ either. __path__ is for distributing a package over multiple directories, and has nothing to do with how you import it. So, yes, please drop it. --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