[Python-Dev] unexpected import behaviour (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Sat Jul 31 17:36:27 CEST 2010
- Previous message: [Python-Dev] unexpected import behaviour
- Next message: [Python-Dev] Proposal: make float.__str__ identical to float__repr__ in Python 3.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Aug 1, 2010 at 1:23 AM, Alexander Belopolsky <alexander.belopolsky at gmail.com> wrote:
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?
"main", so pickling would remain broken. unpickling would at least work correctly under this regime though.
The only way to fix pickling is to avoid monkeying with name at all (e.g. something along the lines of PEP 299, or a special "is_main" flag).
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] unexpected import behaviour
- Next message: [Python-Dev] Proposal: make float.__str__ identical to float__repr__ in Python 3.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]