Hi! I had a problem yesterday where I wanted to extend a top-level module by a module in a subpackage. I naively named my module the same as the toplevel module, and peer import bit me. I finally had to rename my module for no good reason to get things working. So my question is: is there an easy way to force a top-level import (adress the top-level namespace), that I overlooked? If not, what do you think of a from __top__ import systemmodule similar to from __future__ ... An alternative syntax would be "import .systemmodule", but that seems obscure. Ciao, J=FCrgen
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