1.1 --- a/docs/concepts.txt Thu Jun 28 22:58:02 2012 +0200
1.2 +++ b/docs/concepts.txt Fri Jun 29 01:11:02 2012 +0200
1.3 @@ -74,23 +74,23 @@
1.4 completely imported (and thus defined) before an import statement can make it
1.5 available to other modules. Consider the following package root definition:
1.6
1.7 - # Module test:
1.8 + # Module changed:
1.9 def f():
1.10 - import test.modifier
1.11 + import changed.modifier
1.12 x = 123
1.13 f()
1.14
1.15 - # Module test.modifier:
1.16 - import test
1.17 - test.x = 456
1.18 + # Module changed.modifier:
1.19 + import changed
1.20 + changed.x = 456
1.21
1.22 -Here, an import of test will initially set x to 123, but then the function f
1.23 -will be invoked and cause the test.modifier module to be imported. Since the
1.24 -test module is already being imported, the import statement will not try to
1.25 -perform the import operation again, but it will make the partially defined
1.26 -module available for access. Thus, the test.modifier module will then set x to
1.27 -456, and independent modification of the test namespace will have been
1.28 -performed.
1.29 +Here, an import of changed will initially set x to 123, but then the function
1.30 +f will be invoked and cause the changed.modifier module to be imported. Since
1.31 +the changed module is already being imported, the import statement will not
1.32 +try to perform the import operation again, but it will make the partially
1.33 +defined module available for access. Thus, the changed.modifier module will
1.34 +then set x to 456, and independent modification of the changed namespace will
1.35 +have been performed.
1.36
1.37 In conclusion, module globals cannot therefore be regarded as immune to
1.38 operations that would disrupt usage observations. Consequently, only locals