I'm going to guess that you are seeing wxPython bugs. Maybe you are
hitting the problem that wxPython can only be used from the thread
that you original imported wxPython on. If that thread dies you will
see crashes.

                BArry


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin
> Altis
> Sent: 25 June 2001 13:20
> To: Paul Casteels; [EMAIL PROTECTED]
> Subject: RE: debugging wxPython programs
> 
> 
> I have also had problems with PythonWin locking up if I try and run wxPython
> programs. When I made the cwd (current working directory) patch to
> scriptutils.py I noticed that even for non-debugger runs of a program
> PythonWin is execing the code rather than running it as an external program
> 
>     codeObject = compile(f.read()+"\n", script, "exec")
> ...
>     exec codeObject in __main__.__dict__
> 
> Given that wxPython wraps wxWindows which uses native widgets... I wouldn't
> be surprised if this model causes conflicts with PythonWin.
> 
> Anyway, my solution so far has been to edit in PythonWin with an Explorer
> window and a command-shell open to the directory my source is in. After I do
> a save, I switch to the command-shell and run the new version. That avoids
> any conflicts with PythonWin.
> 
> ka
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Paul
> > Casteels
> > Sent: Monday, June 25, 2001 12:32 AM
> > To: [EMAIL PROTECTED]
> > Subject: debugging wxPython programs
> >
> >
> >
> >  I have a small script that uses the wxPython (2.3.0)library. I can run
> > this without any problems in the IDLE environment, but with PythonWin
> > there is a crash after the third run : The instruction at 0x1e132ecd
> > referenced memory at 0x00014. The memory could not be read. The program
> > even runs with the "No Debugging" option.
> >  All I can do is kill PythonWin with the TaskManager (I use Windows2000).
> > I have this problem with release 210 and 211. In general PythonWin seems
> > unstable with wxWindows, but with this script I can reproduce the crash.
> >  Is this a known problem with PythonWin/wxPython ? Is there another way to
> > debug wxPython programs ?
> >
> > Paul Casteels               [EMAIL PROTECTED]  Tel: +32.3.8202455
> >                                             Fax: +32.3.8202470
> > University of Antwerp       Dpt.Physics
> > Universiteitsplein 1
> > B-2610 Wilrijk
> > Belgium
> >
> > _______________________________________________
> > ActivePython mailing list
> > [EMAIL PROTECTED]
> > http://listserv.ActiveState.com/mailman/listinfo/activepython
> >
> 
> _______________________________________________
> ActivePython mailing list
> [EMAIL PROTECTED]
> http://listserv.ActiveState.com/mailman/listinfo/activepython
> 
> 
_______________________________________________
ActivePython mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/activepython

Reply via email to