Re: [Matplotlib-users] plotting from xemacs always 1 step behind

2008-02-18 Thread Neal Becker
On Tuesday 12 February 2008, John Hunter wrote: > On Feb 12, 2008 6:49 AM, Neal Becker <[EMAIL PROTECTED]> wrote: > > This is a bit wierd. > > > > If running from xemacs, it seems interactive plotting is always 1 step > > behind. > > I assume you have set 'interactive : True' in your rc file? What

Re: [Matplotlib-users] plotting from xemacs always 1 step behind

2008-02-12 Thread Phil Austin
John Hunter wrote: > On Feb 12, 2008 12:17 PM, Neal Becker <[EMAIL PROTECTED]> wrote: > >> If invoked from M-x py-shell doesn't work. >> >> Now if I could just figure out where to modify the way py-shell invokes >> ipython to add the -pylab. Doc say C-u M-x py-shell would prompt for args,

Re: [Matplotlib-users] plotting from xemacs always 1 step behind

2008-02-12 Thread John Hunter
On Feb 12, 2008 12:17 PM, Neal Becker <[EMAIL PROTECTED]> wrote: > If invoked from M-x py-shell doesn't work. > > Now if I could just figure out where to modify the way py-shell invokes > ipython to add the -pylab. Doc say C-u M-x py-shell would prompt for args, > but the doc lies. You can proba

Re: [Matplotlib-users] plotting from xemacs always 1 step behind

2008-02-12 Thread Neal Becker
Phil Austin wrote: > John Hunter wrote: > > > > Well, the problem is that GTK, WX and Qt require threading support to > > use them properly interactively. ipython has special modes for these > > to run the GUI mainloop in the separate thread. tk is special in this > > regard, in that it run

Re: [Matplotlib-users] plotting from xemacs always 1 step behind

2008-02-12 Thread Phil Austin
John Hunter wrote: > > Well, the problem is that GTK, WX and Qt require threading support to > use them properly interactively. ipython has special modes for these > to run the GUI mainloop in the separate thread. tk is special in this > regard, in that it runs from a standard python shell w

Re: [Matplotlib-users] plotting from xemacs always 1 step behind

2008-02-12 Thread John Hunter
On Feb 12, 2008 8:50 AM, Neal Becker <[EMAIL PROTECTED]> wrote: > I did set interactive. > > I was using QtAgg. > > I hate tk. [reposting in the correct thread] Well, the problem is that GTK, WX and Qt require threading support to use them properly interactively. ipython has special modes for t

Re: [Matplotlib-users] plotting from xemacs always 1 step behind

2008-02-12 Thread John Hunter
On Feb 12, 2008 6:49 AM, Neal Becker <[EMAIL PROTECTED]> wrote: > This is a bit wierd. > > If running from xemacs, it seems interactive plotting is always 1 step > behind. I assume you have set 'interactive : True' in your rc file? What backend are you using (you should be using tkagg from xemacs

[Matplotlib-users] plotting from xemacs always 1 step behind

2008-02-12 Thread Neal Becker
This is a bit wierd. If running from xemacs, it seems interactive plotting is always 1 step behind. For example, I do: M-x py-shell This brings up a *Python* buffer in Comint mode running Ipython. In [1]: from pylab import * In [2]: plot ([1,2,3]) Out[2]: [] In [3]: xlabel('time') Out[3]: I