[IPython-dev] IPython proposal: getting rid of "ipython -pylab\-wthread\etc."

So, ... I am dumb, and I haven't been following things well enough (not
enough time). Concretely, what do I need to do to be able to launch
IPython, and pop up a wx dialog not blocking IPython with the new
technology?

Gaël

···

On Thu, Jul 16, 2009 at 08:28:11PM +0300, Ville M. Vainio wrote:

On Thu, Jul 16, 2009 at 8:20 PM, Gael > Varoquaux<gael.varoquaux@...427...> wrote:

> Would it be possible for IPython to expose both solutions for a while
> (say 6 month to a year), so that we all have time to adapt?

You can start adapting already, as indicated in previous post. Just
adjust the embedding code, and any old version of ipython will work.

Good question Gael,

So, … I am dumb, and I haven’t been following things well enough (not

enough time). Concretely, what do I need to do to be able to launch

IPython, and pop up a wx dialog not blocking IPython with the new

technology?

If you have a patched version of wx (that Robin and I are working on) you just do the following (from either ipython or python!):

import wx
app = wx.IApp(clearSigInt=False) # for interactive app

then you are off to the races (you don’t even need to start the mainloop)

With current versions of mpl, you can do:

import wx
app = wx.IApp(clearSigInt=False)
from matplotlib import pyplot as plt

plt.interactive(True)
the everything just works…

Obviously, the creation of the IApp object should be put into the GUI toolkit initialization code in mpl/mayavi/etc. I will work with Robin to get a version of wx posted that has the patched applied so people can begin to test this.

Cheers,

Brian

OK, that's great. It enlightens me. So, it seems you guys are on the
right track. I'll just wait for the new versions of wx to come out. You
are doing great work on that.

One piece of warning: Wx has a terrible upgrade path. Upgrading it breaks
stuff. As a consequence, people don't upgrade it often, and my experience
is that we have to maintain compatibility with old version for years (at
least 3 years: in Ubuntu, latest release, installing SPE drags along
wxPython 2.6, and thus people find themselves importing this version
without realizing it).

Ga�l

···

On Thu, Jul 16, 2009 at 10:45:04AM -0700, Brian Granger wrote:

   Obviously, the creation of the IApp object should be put into the GUI
   toolkit initialization code in mpl/mayavi/etc.� I will work with Robin to
   get a version of wx posted that has the patched applied so people can
   begin to test this.

OK, that’s great. It enlightens me. So, it seems you guys are on the

right track. I’ll just wait for the new versions of wx to come out. You

are doing great work on that.

Thanks.

One piece of warning: Wx has a terrible upgrade path. Upgrading it breaks

stuff. As a consequence, people don’t upgrade it often, and my experience

is that we have to maintain compatibility with old version for years (at

least 3 years: in Ubuntu, latest release, installing SPE drags along

wxPython 2.6, and thus people find themselves importing this version

without realizing it).

This is good to know.

Cheers,

Brian

···

Gaël