Crash again and again?

[Gavin]

I run a simple wxPython demo with PyScripter and it crashed when I
clicked 'Run' button again after I closed the demo program.
When I tried to 'Run' the demo in a second time, a new empty window
flashed and the windows has '_wxwindows.py' in its Tab. Then the
PyScripter crashed and hanged. I can only kill the process.

Below is my test script(I don't think it's my code's fault 'cause I
stolen the scipter from the book.):

#!/bin/env python
import wx
class MyFrame(wx.Frame):
def __init__(self):
wx.Frame.__init__(self, None, -1, "My Frame", size=(300, 300))
panel = wx.Panel(self, -1)
panel.Bind(wx.EVT_MOTION, self.OnMove)
wx.StaticText(panel, -1, "Pos:", pos=(10, 12))
self.posCtrl = wx.TextCtrl(panel, -1, "", pos=(40, 10))
def OnMove(self, event):
pos = event.GetPosition()
self.posCtrl.SetValue("%s, %s" % (pos.x, pos.y))
if __name__ == '__main__':
app = wx.PySimpleApp()
frame = MyFrame()
frame.Show(True)
app.MainLoop()

[Gavin]

Forgot to descript the env:
WinXP pro sp2
PyScripter 1.9.9.2
And the demo works well in SPE.

[Clemens Anhuth]

Gavin wrote:
> I run a simple wxPython demo with PyScripter and it crashed when I
>

Hello Gavin,

did you follow the information in the online manual/help? See "Running
Python Engines" / "Remote Python Engines":

Remote Python Engines
Previous <runconfigurations.htm> Top <pyscripter.htm> Next
<postmortemanalysis.htm>

------------------------------------------------------------------------
In addition to using the internal integrared Python engine, PyScripter
offers you the option to use one of three remote Python engines. These
remote engines run in a separate process, so, when using them, script
errors should not affect the stability of PyScripter. You can select
the python engine that will be active from the Python Engine submenu of
the Run menu <runmenu.htm>. Here is a brief explanation of the Python
engine options:

*Python Engines:*

· *Internal*

This the default engine of PyScripter. It is faster than the other
options however if there are problems with the scripts you are running
or debugging they could affect the reliability of PyScripter and could
cause crashes. Another limitation of this engine is that it cannot run
or debug GUI scripts nor it can be reinitialized.

· *Remote*

This is the standard remote Python engine. It runs in a child process
and communicates with PyScripter using Rpyc <http://rpyc.sf.net>. It
can be used to run and debug any kind of script. However /_if you run
or debug GUI scripts you may have to reinitialize the engine after each
run_//./

· *Remote Tk*

This remote Python engine is specifically created to run and debug
Tkinter applications including pylab
<http://matplotlib.sourceforge.net/> using the Tkagg backend. It also
supports running pylab in interactive mode. The engine activates a
Tkinter mainloop and replaces the mainloop with a dummy function so that
the Tkinter scripts you are running or debugging do not block the
engine. You may even develop and test Tkinter widgets using the
interactive console.

· *Remote Wx*

This remote Python engine is specifically created to run and debug
wxPython <http://www.wxpython.org/> applications including pylab
<http://matplotlib.sourceforge.net/> using the WX and WXAgg backends. It
also supports running pylab in interactive mode. The engine activates a
wx MainLoop and replaces the MainLoop with a dummy function so that the
wxPython scripts you are running or debugging do not block the engine.
You may even develop and test wxPython Frames and Apps using the
interactive console. Please note that this engine prevents the
redirection of wxPython output since that would prevent the
communication with Pyscripter.

When using the Tk and Wx remote engines you can of course run or debug
any other non- GUI Python script. However bear in mind that these
engines may be slightly slower than the standard remote engine since
they also contain a GUI main loop. Also note that these two engines
override the sys.exit function with a dummy procedure.

*Debugging Wx and Tkinter scirpts using the remote Wx and Tk engines*

As mentioned above the Wx and Tk engines activate a main loop and
replace the MainLoop with a dummy function. Therefore, when debugging
Gui scripts using these engines, as soon as you reach the MainLoop
statement debugging ends and you can then test the running application
but without further debugging support. This means two things:

· Breakpoints and debugging would work up to the point the script
enters the MainLoop routine
· You will not be able to debug event triggered code using these
two engines.

To debug event code of Wx and Tkinter scripts use the standard remote
engine. You may wonder why should you ever use the Wx and Tk specific
remote engines. Here is a few reasons:

· These engine allow you to interactively develop and test frames
and widgets. (possible because they run their own main loop.
· They support running pylab in interactive mode like IPython does,
which was a request from many Pyscripter users.
· There is no need to reinitialize the engines after running Gui
scripts.
· Pyscripter does not stay in running mode while the Gui Windows
are showing but instead it returns in ready mode allowing further work
and runs.

*Requirements for the Remote Engines*

The remote engines require the installation of Rpyc <http://rpyc.sf.net>
version 2.6, which by the way is just brilliant.. If you are running
Python 2.3 then you may try to install the back ported version 2.55,
although this combination has not been tested.

*Troubleshooting*
*
*
· If the remote Python engine becomes unresponsive you can try to
reinitialize the engine from the Python Engine submenu of the Run menu
<runmenu.htm> (also available in the context menu of the interactive
interpreter <pythoninteractiveinterpreter.htm>).
· If Pyscripter fails to start or appears locked when starting this
may be due to remote python engines from earlier runs still being
active. This could happen after a Pyscripter crash. In such cases you
should kill the python engines using the Windows Task Managers. Look in
the Processes tab for processes with image name "pythonw.exe".

With best regards

Clemens Anhuth

[Gavin]

Thanks. It really helps but the remote engine still could not be
activated after I installed the Rpyc (3.01). Do I need a restart
after installation?

[Clemens Anhuth]

*Requirements for the Remote Engines*

[Clemens Anhuth]

Checking the RPyC site I noticed that it eventually leads to a
sourceforge page which only lists RPyC 3.01. On that page click
"Download" / "Browse All Packages" or go directly here:

http://sourceforge.net/project/showfiles.php?group_id=155578

This page lists the download for RPyc 2.6.

[PyScripter]

I have put the Rpyc version 2.6 for Python 2.4-2.6 in the pyscripter
Google code site http://code.google.com/p/pyscripter/downloads/list.
I will move to Rpyc version 3.0 in the near future.