no. it works the way it's intended to work. given that order of module imports is not defined (i.e. reordering imports should not affect resulting code), making 'version=' propagating to other modules will create disasterous side effects, even weirder than C macro abusing.
Okay, thanks for the explanation. I hadn't considered that putting a version assignment between imports, but I see how that can become an issue.
