Python scope / namespace issue?

This one works fine without complicating your code: funcs. Py import classes def func(): d = classes.D() print "func" if __name__ == "__main__": c = classes.C() classes. Py import funcs class C: def __init__(self): print "C class" funcs.func() class D: def __init__(self): print "D class Sometimes it's much better to use simple import, than from ... import There is quite good article on that: effbot.org/zone/import-confusion.htm.

This one works fine without complicating your code: ///funcs. Py import classes def func(): d = classes.D() print "func" if __name__ == "__main__": c = classes.C() ///classes. Py import funcs class C: def __init__(self): print "C class" funcs.func() class D: def __init__(self): print "D class" Sometimes it's much better to use simple import, than from ... import .... There is quite good article on that: effbot.org/zone/import-confusion.htm.

The problem occurs due to the attempt to use a cyclically imported module during module initialization. To clarify, using the "from module use *" requires that a module be compiled. Instead if you switch to using "import module" in both cases, it should work fine.

1 "requires that a module be compiled" is misleading at best. The module code is loaded, compiled and run either way. But from m import * copies everything that's in the module at that point in time while import m gives a reference to the module object - and hence makes later modifications visible.

– delnan Aug 29 at 10:18.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.