> Well, ... I've managed to crash python by using an "ostream" rather than
> "printf". The code is below. If I replace the std::cout with a printf
> the code works fine. The symptom is that the cout is flushed to the
> console as it should be, then the python shell hangs. A few seconds
> later
Another option might be to wrap your C code using the ctypes module (
http://starship.python.net/crew/theller/ctypes/). This might be especially attractive if this code is mostly for demo purposes (at least for demo purposes on win32). Ctypes basically allows you to call C code from python, but r
