>>>>> "MAL" == M -A Lemburg <mal@lemburg.com> writes: >> Modified Files: compile.c Log Message: Enforce two illegal import >> statements that were outlawed in the reference manual but not >> checked: Names bound by import statemants may not occur in global >> statements in the same scope. The from ... import * form may only >> occur in a module scope. >> >> I guess these changes could break code, but the reference manual >> warned about them. MAL> Jeremy, your code breaks all uses of "from package import MAL> submodule" inside packages. MAL> Try distutils for example or setup.py.... Quite aside from whether the changes should be preserved, I don't see how "from package import submodule" is affected. I ran setup.py without any problem; I wouldn't have been able to build Python otherwise. I wrote some simple test cases and didn't have any trouble with the form you describe. Can you provide a concrete example? It may be that something other than the changes mentioned above that is causing you problems. Jeremy
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