[wxPython-users] QME-Dev Workbench (wxSciPy) Beta 2.7 - RELEASED TODAY on sourceforge

[Josiah Carlson]

Robert VERGNES <robert.vergnes at yahoo.fr> wrote:
> *Externally Processed Python Shells: 
> You can now Run several VERY long tasks and keep working with the wxGUI ! 
> Thank you to Josiah Carlson for his library and help on this issue. It is now functional.
> The advantage of externally processed Python Shells is that you can start long tasks 
> and the wxGUI is not blocked or frozen. So you can use it to plot, prepare your script or 
> do other things such as export/import data etc... (tested with 5 shells running on long 
> tasks > 35min, tested:solo-long task > 1hr). In fact the Python Shell windows in the main 
> application are just terminals to the underlying Python Shells... which are external 
> process to the application. The python shell windows you see are not the shells,.. 
> this is clever.. and it does work nicely. Again. Thank you Josiah !

For reference, the code that is being used for this is more or less the
same code that is used in PyPE, only extracted from base PyPE to be used
by other applications.  Part of that extraction is that the code really
hasn't been cleaned up (it was pretty hackish in PyPE, moreso in the
extracted variant).  However, if you *really* want to try the shells by
themselves (no introspection like other shells based on wx.py.shell,
very simple facade), you can extract the 'plugins' portion of QME-Dev
and run 'interpreter.py'.

For real introspection, better code organization, and a more or less
drop-in replacement for wx.py.shell, I've got an application in for a
Google SoC project.

In the mean time, enjoy QME-Dev.


 - Josiah