@bmispelon My thought would be Python:
- runs c.py and immediately starts to import a.py
- sets `A` to 1
- then starts to import b.py
- module a(.py) is already in memory, so it bumps A to 2
- finished importing b and a
- returns to c.py and prints 2
_chrismay@fosstodon.org
@_chrismay@fosstodon.org
Posts
-
Can someone explain this #Python import behavior -
Unfortunately the relative quiet of the last few days is over.@inthehands Thanks for letting us know. It's heartbreaking, but important to know what's going on.