This is an ugly situation: I've got a wxPython-based Windows app.
Now on to the really ugly part...
The Python code spits out diagnostic info via print statements.
Normally, these would never be seen by users, but when we are
developing they are invaluable. We have special glue to create a
Windows console when given a particular command line option so
this is what we use during development.
However, running without the console window causes the application
to crash when certain particular print statements are encountered.
We have absolutely no idea how to diagnose this one. Why does
Windows not just ignore these statements (/dev/null them)? Is there
a way to make it ignore them?
···
-------------------------------------------------------------------------------------
Jeff Kotula Systems Architecture Manager
Vital Images jkotula@vitalimages.com
Renunciation is not giving up the things of this world,
but accepting that they go away.
-- Suzuki Roshi