RE: debugging wxPython programs

2001-06-26 Thread Barry Scott
L 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

Re: debugging wxPython programs

2001-06-25 Thread Paul Prescod
Paul Casteels wrote: > >... > Is this a known problem with PythonWin/wxPython ? Is there another way to > debug wxPython programs ? In general, it is not safe to debug graphical applications using "foreign" toolkits in IDLE or PythonWin. If you've had luck so far with IDLE, that's fine, but it

RE: debugging wxPython programs

2001-06-25 Thread Kevin Altis
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 environme

debugging wxPython programs

2001-06-25 Thread Paul Casteels
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