On Feb 23, 6:44 am, Boris Ozegovic <[EMAIL PROTECTED]>
wrote:
> Can somebody explaint this to me:
>
> I have module a.py
> A = 100
> import b
> print "A printing"
> print "B is %s" % b.B
>
> and module b.py
> B = 2000
> import a
> print "B printing"
> print "A is %s" % a.A
>
> I thought that output
Diez B. Roggisch wrote:
> I use it sometimes myself, to avoid otherwise circular imports.
Circular imports are the reason why I have module issues. Last question:
if I put modules in some package and then try to import one I get
"AttributeError: 'module' object has no attribute 'a'
Code is:
a
Boris Ozegovic wrote:
> Diez B. Roggisch wrote:
>
>> Are you sure the above is what you really used for your test? Because
>> your output features a single 100, which the above lacks a
>> print-statement for.
>
> Yeah, I cancelled the message, but synchronization allready happened. :)
>
> Prob
Diez B. Roggisch wrote:
> Are you sure the above is what you really used for your test? Because your
> output features a single 100, which the above lacks a print-statement for.
Yeah, I cancelled the message, but synchronization allready happened. :)
Problem was in some other place.
One more q
Boris Ozegovic wrote:
> Can somebody explaint this to me:
>
> I have module a.py
> A = 100
> import b
> print "A printing"
> print "B is %s" % b.B
>
> and module b.py
> B = 2000
> import a
> print "B printing"
> print "A is %s" % a.A
>
> I thought that output would be:
> B printing
> A is 100
>
Can somebody explaint this to me:
I have module a.py
A = 100
import b
print "A printing"
print "B is %s" % b.B
and module b.py
B = 2000
import a
print "B printing"
print "A is %s" % a.A
I thought that output would be:
B printing
A is 100
A printing
B is 2000
Because import b would execute b.py,
