Re: A thread import problem
On Sun, 22 Jul 2012 13:04:25 -0600, Bruce Sherwood
<email@example.com> declaimed the following in
> Another way of saying this is that I'm not building an app, in which
> case I would structure things in a simple and straightforward manner.
> I am instead trying to maintain and update a library that allows
> novice programmers to write programs that generate real-time navigable
> 3D animations, writing minimalist programs that work cross-platform.
I suspect you don't need to update the library so much as enforce a
project style that prevents your import-thread-import cycle. In short,
something like that hypothetical "runner()" design.
Oh, and document that style in detail: "importable modules shall
only perform module level definition of entities during import -- no
code that actually processes data"; "importable modules shall make use
of the 'if __name__ == "__main__": main()' convention to identify when
the module is being used stand-alone, and thereby invoke the main
processing; otherwise the module.main() function is to be invoked only
be the module doing the imports, after the import has completed"
Wulfraed Dennis Lee Bieber AF6VN