2.1.1 global weirds

Robin Becker robin at jessikat.fsnet.co.uk
Mon Aug 13 03:58:33 EDT 2001


In article <9l6jts0tb3 at enews2.newsguy.com>, Alex Martelli
<aleaxit at yahoo.com> writes
>"Robin Becker" <robin at jessikat.fsnet.co.uk> wrote in message
>news:6Def3XA5vnd7Ewrz at jessikat.fsnet.co.uk...

>because there's a sys.modules['__main__'] but NOT yet a
>sys.modules['a'] -- so b CAN use a's stuff after import a IF
>b has been imported from the main module.  Clearer now?
>
....
well as is clear you always respond to the current situation whereas I'm
considering a hypothetical. Following one's nose leads to short
sightedness.

>> There's probably some reason for allowing A.B and B to have the same
>> module source and be different modules, but I don't know what it is. The
>
>I've been trying to explain it for the last zillion posts in this
>thread, and I get the strong impression that I'm not getting
>through, so maybe you STILL don't know it despite by best
>efforts -- so, I give up.
...
I give up too, playing dumb isn't useful.
-- 
Robin Becker



More information about the Python-list mailing list