make compiled in python extension initialization more flexable
authorDiane Trout <diane@caltech.edu>
Tue, 5 Dec 2006 23:54:57 +0000 (23:54 +0000)
committerDiane Trout <diane@caltech.edu>
Tue, 5 Dec 2006 23:54:57 +0000 (23:54 +0000)
commit90c246fb6284a6d191eed079f73c38812092a4b9
tree578ce6501d1e2827d893d2f68a672032d93af51b
parent7c3bf26770d10c90e1b40c60479114f42a84edf0
make compiled in python extension initialization more flexable
Because of weird library ordering issues, my test case that tested
running python code was looking for compiled in python modules that
weren't available yet it wouldn't link properly.

I solved this by making it possible to provide a list of what
compiled-in python extensions should be initialized when you launch
the interpreter, so the mussagl program, which does have all the right
components linked in is what is specifying what modules should be
provided to the python interpreter.

Now I just need to fix the build system so you can compile mussa without
all this python crud if needed.

And maybe decide how to launch the gui from a stanard python interpreter.
py/CMakeLists.txt
py/python.cpp
py/python.hpp
py/test/test_python.cpp
qui/mussagl.cpp
qui/threading/InterpreterThread.cpp
qui/threading/InterpreterThread.hpp
qui/threading/ThreadManager.cpp
qui/threading/ThreadManager.hpp