[Python-Dev] unexpected import behaviour (original) (raw)
Alexander Belopolsky alexander.belopolsky at gmail.com
Sat Jul 31 17:23:27 CEST 2010
- Previous message: [Python-Dev] unexpected import behaviour
- Next message: [Python-Dev] unexpected import behaviour
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Jul 31, 2010 at 11:07 AM, Nick Coghlan <ncoghlan at gmail.com> wrote: ..
That said, I really don't think catching such a rare error is worth any runtime overhead. Just making "main" and the real module name refer to the same object in sys.modules is a different matter, but I'm not confident enough that I fully grasp the implications to do it without gathering feedback from a wider audience.
If you make sys.module['main'] and sys.module['modname'] the same (let's call it mod), what will be the value of mod.name?
- Previous message: [Python-Dev] unexpected import behaviour
- Next message: [Python-Dev] unexpected import behaviour
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]