Jim Fulton wrote: > > "M.-A. Lemburg" wrote: > > In the end, having written a self-contained package is a "feature" > > of that package. Other authors can then say: ok, I can > > plugin your package if it's self-contained. > > Well said. It really should be possible to provide > *self-contained* package hierarchies. > There are at > least two people in this discussion that are trying hard to > make use of packages and have observed a significant problem. OK, just to make sure I understand this. You are saying that a ".." operation is needed in imports so that a package author with a package which looks like this: mypackage mypackage/sub1/mod1.py mypackage/sub2/mod2.py can write "import __.sub2.mod2" instead of "import mypackage.sub2.mod2" within the file mod1.py. Right? Jim Ahlstrom
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