On Wed, Jul 4, 2012 at 11:11 PM, Jorge Scandaliaris <jorgesmbox-ml@yahoo.es> wrote:
> De: Tony Yu <tsyu80@gmail.com>
>Just a wild guess: Any chance you're using some GUI-toolkit-specific functionality?

Can you elaborate please? I use the GTKAgg backend, and I guess IPython has specific mechanisms (I don't know the details) for keeping both the plot and the interpreter responsive, that's the --pylab option I mention. However, why am I the only asking for help here? Is it that just a few people use events and gtk backend and IPython?
My script, although larger and by now more complex, follows the lines of the example I gave earlier...


Sorry, I wasn't suggesting that it was a problem with the GTK backend; I was asking if you were explicitly calling GTK.

IPython --pylab starts an event loop for the default matplotlib backend (you can check this by printing `plt.rcParams['backend']`). If for some reason your default backend is not GTK and --pylab starts an event loop for that backend, then GTK-specific calls could cause problems. If this is the problem, you could set the backend in your matplotlibrc file. Alternatively, IPython has a -gthread command line option.

Like I said, this just a wild guess. Without example code, it's hard to pin down.


P.S. sorry for the duplicate, Jorge. I forgot to reply-all.