Aahz <aahz at pythoncraft.com>: > Between the addition of ``as`` in Python 2.0 and the new syntax & > semantics for ``import``, there is no longer a need for ``__path__``, and > it is now officially deprecated. NO! WAIT! I have a project in which I'm modifying a module's __path__, and it's *not* to work around any deficiencies in the relative import mechanism. Rather it's to make a set of directories behave like a single package for import purposes, with the members of the set determined at run time. Will there be any easy way to do this under the new scheme? If not, can you please try to find some way to make __path__ work sensibly with the new rules. Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg at cosc.canterbury.ac.nz +--------------------------------------+
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