I think what your looking for is to create your application object with a 0
as the input parameter, like: app = wxPySimpleApp(0). That will keep
wxPython from sending stdout and stderr to a window. Also change your
console window settings to have a fairly large buffer so that don't loose
the beginning of the error messages if you generate a lot of them.
Living with windowsly,
Tom Fenn
Chris Barker
<chrishbarker@h To: wxpython-users@lists.wxwindows.org
ome.net> cc: (bcc: Tom Fenn/US-Corporate/3M/US)
10/23/01 01:39
PM
Please respond
to
wxpython-users
Hi all,
I've been using wxPython for a while on Linux, but I'm having trouble
finding a productive way to work on Windows.
So far, we have been doing most of our Python work in PythonWin, which
has worked pretty well. Now that we are using wxPython, however, this
won't work. I imagine it's the old event-loop interaction again. So the
solution is to run the python program at the command line. The problem
we have there (besides the fact that the DOS/Win command line sucks), is
that when wxPython starts up, it captures stderr to a windows window,
and when the program crashes, that window closes, so we can't even see
what the error was when it crashed.
Anyway, there must be a productive way to work with wxPython on
Windows...what are you all doing?
thanks,
Chris
···
Subject: [wxPython] How to use wxPython on Windows
--
Christopher Barker,
Ph.D.
ChrisHBarker@home.net --- --- ---
http://members.home.net/barkerlohmann ---@@ -----@@ -----@@
------@@@ ------@@@ ------@@@
Oil Spill Modeling ------ @ ------ @ ------ @
Water Resources Engineering ------- --------- --------
Coastal and Fluvial Hydrodynamics --------------------------------------
------------------------------------------------------------------------
_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users