At 16:55 17.05.2004 +0200, M.-A. Lemburg wrote: >Phillip J. Eby wrote: >>At 03:42 PM 5/17/04 +0200, M.-A. Lemburg wrote: >> >>>I have a few questions about the PEP 328 which I'd like discussed: >>> >>>* Why do we absolutely need to change the current scheme >>> of 'local, then absolute' for name resolution ? >>Because there's no way to override the current scheme without calling >>__import__ directly. > >Are you saying that you are not going to change the default __import__() >implementation, only the way it is called ? (I wonder how you'll >enforce the 'absolute only' strategy then) if you pass globals = {} you get absolute imports from __import__, It is probably true that in the long run, given the new semantics, moving responsabilities away from/changing __import__ contract could make sense.
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