jean-marc wrote:
> Merci Bruno, ( and also to Fredrik )
>
> So I think I understand correctly, if I say that:
> each modulkes requires its own set of reference to whatever objects it
> needs to speak. The interpreter wil see not to create extra copies of
> the compiled code if many modules import
Merci Bruno, ( and also to Fredrik )
So I think I understand correctly, if I say that:
each modulkes requires its own set of reference to whatever objects it
needs to speak. The interpreter wil see not to create extra copies of
the compiled code if many modules import the same modules but will mak
jean-marc wrote:
> As an application programmer, I'm not well versed in the material
> aspects of computing (memory, cpu, bus and all). My understanding of
> imports in Python is such: the __main__ program is the center piece
> which holds the programs reference: globals, functions, classes,
> modu
"jean-marc" wrote:
> BUT, of all this I thought that if you import module1, then module2
> (into __main__), objects from module1 would be available to objects of
> module2 which came (into memory space) after module1 was loaded. This
> does not seem to be the case, and module2 requires an 'import
