[Python-ideas] PEP for executing a module in a package containing relative imports (original) (raw)
Christian Heimes lists at cheimes.de
Sun Apr 22 20:54:57 CEST 2007
- Previous message: [Python-ideas] PEP for executing a module in a package containing relative imports
- Next message: [Python-ideas] PEP for executing a module in a package containing relative imports
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brett Cannon wrote:
* name is never mangled and contains always the dotted name of the current module. It's not set to 'main' any more. That can't be true. If I am in the directory /spam but I execute the file /bacon/code.py, what is the name of /bacon/code.py supposed to be? It makes absolutely no sense unless sys.path happens to have either / or /bacon. This is why I wondered out loud if setting whatever attribute that is chosen not to main should only be done with '-m' as that keeps it simple and clear instead of having to try to reverse-engineer a file's name attribute.
I haven't thought of that issue. :(
* I'm against sys.modules['main] = mainmodule because it may cause ugly side effects with reload. I assume that key is a string? There is a single quote that is not closed off.
Yes, it's a typo. It should say sys.modules['main'].
I am totally fine if people propose a competing PEP or try to resurrect PEP 299, but I am not going to be the person who does that leg work.
Understood! :)
Christian
- Previous message: [Python-ideas] PEP for executing a module in a package containing relative imports
- Next message: [Python-ideas] PEP for executing a module in a package containing relative imports
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]