[wxPython] How to use wxPython on Windows

I use editors that can capture output:

EditPlus is a very good one (comercial): http://www.editplus.com
ConTEXT is another alternative (free) : ::fixedsys.com::

···

-----Original Message-----
From: Chris Barker [SMTP:chrishbarker@home.net]
Sent: Tuesday, October 23, 2001 3:40 PM
To: wxpython-users@lists.wxwindows.org
Subject: [wxPython] How to use wxPython on Windows

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

--
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

Thanks to all of you who replied this question, I think I've got it
figured out now.

I'm actually doing very little with Windows at all, most of the windows
stuff is being done by a couple of my coleagues, that don't have the
benefit of the *nix experience. If I had to use Windows a lot, I'd
definately give CygWin a try. Thanks for all the info about it and other
options

pfenn@mmm.com wrote:

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.

BINGO! That's it! We had: app = App(1)

All the other advice is helpfull, but this was the big one that was
confusing me!

Thanks all,

-Chris

···

--
Christopher Barker,
Ph.D.
ChrisHBarker@home.net --- --- ---
http://members.home.net/barkerlohmann ---@@ -----@@ -----@@
                                   ------@@@ ------@@@ ------@@@
Oil Spill Modeling ------ @ ------ @ ------ @
Water Resources Engineering ------- --------- --------
Coastal and Fluvial Hydrodynamics --------------------------------------
------------------------------------------------------------------------