Hi all,
I've update matplotlib to the git version of the software (1.4.x), after
updating it the interactive mode on ipython stopped working.
I'll briefly show what happens:
$ ipython -- pylab
Python 2.7.3 (default, Feb 27 2014, 19:58:35)
Type copyright, credits or license for more
0.12.1 is a very old version of ipython. I know there have been some
changes to matplotlib to deal with changes that ipython has made over the
past two years, but I did think that they were all backwards compatible.
@mdboom, do you think this could be related to that fix we made on
detecting
Yes! It was ipython issue!
I was convinced that my version were the github one!!! I'm sorry!
Thank you for the quick response!
Roberto
--
View this message in context:
http://matplotlib.1069221.n5.nabble.com/ipython-pylab-interactive-mode-problem-tp43144p43149.html
Sent from the matplotlib
On Mon, Dec 10, 2012 at 5:49 PM, Timothy Duly timdu...@gmail.com wrote:
Paul,
Actually, I didn't realize that you had to change the backend in the
matplotlibrc file. Once I changed it to 'Qt4Agg', everything worked.
Thanks!
(to find out where your matplotlibrc file is:
On Mon, Dec 10, 2012 at 12:15 PM, Timothy Duly timdu...@gmail.com wrote:
Hi,
I recently upgraded to matplotlib v1.2.0 on my Linux machine. For some
reason, plots are not appearing at all on my screen whenever I try to plot
any routines.
When I open the interpreter with ipython --pylab and
Paul,
I am using the agg backend:
In [1]: import matplotlib
In [2]: matplotlib.rcParams['backend']
Out[2]: 'agg'
I was able to switch it to the one you have:
In [12]: import matplotlib
In [13]: matplotlib.rcParams['backend'] = 'Qt4Agg'
but still a simple plot(1,1) resulted in no plot being
Paul,
Actually, I didn't realize that you had to change the backend in the
matplotlibrc file. Once I changed it to 'Qt4Agg', everything worked.
Thanks!
(to find out where your matplotlibrc file is:
matplotlib.matplotlib_fname() )
Tim
On Mon, Dec 10, 2012 at 2:34 PM, Timothy Duly
Hi all,
It's exactly as said. I am using OS 10.6
If I use ipython -pylab and later try to plot anything, the GUI for plotting
launches and I just get a beachball.
However, if I do ipython and then import plot, I can do a plot with no problem.
I did a search but came up with nothing. I have
On Thu, Feb 17, 2011 at 3:56 AM, Matthias Wong arkan...@gmail.com wrote:
Hi all,
It's exactly as said. I am using OS 10.6
If I use ipython -pylab and later try to plot anything, the GUI for
plotting launches and I just get a beachball.
However, if I do ipython and then import plot, I can
Matthias Wong, on 2011-02-17 20:56, wrote:
Hi all,
It's exactly as said. I am using OS 10.6
If I use ipython -pylab and later try to plot anything, the GUI for plotting
launches and I just get a beachball.
However, if I do ipython and then import plot, I can do a plot with no
hello,
I get a segmentation fault with the pylab mode and I made several
test to track down a bug but it's beyond my level and I still don't now
if it's an ipython bug or matplotlib bug ...
let's reproduce the bug
/ try 1 Qt4Agg \_
phil@Numokh ~ % ipython
I have seen this problem when matplotlib wasn't fully rebuilt after
upgrading Numpy. I would assume, since you're installing from Gentoo
packages, that the package manager is smart enough to blitz the
matplotlib build products before rebuilding, but maybe not. (Python
distutils doesn't do
Le Tue, 08 Feb 2011 09:14:22 -0500,
Michael Droettboom md...@stsci.edu a écrit :
I have seen this problem when matplotlib wasn't fully rebuilt after
upgrading Numpy. I would assume, since you're installing from Gentoo
packages, that the package manager is smart enough to blitz the
Dear all,
maybe this should go to the Enthought list, but as the failure is directly
related to the pylab switch of ipython, I thought I try it here first:
On OSX I have trouble with using the pylab switch for ipython after I copied
the gdal.pth into the Enthought site-packages folder (to be
On 2010-04-13 10:18 AM, K. -Michael Aye wrote:
Dear all,
maybe this should go to the Enthought list, but as the failure is directly
related to the pylab switch of ipython, I thought I try it here first:
On OSX I have trouble with using the pylab switch for ipython after I copied
the
On 2010-04-13 10:18 AM, K. -Michael Aye wrote:
Dear all,
maybe this should go to the Enthought list, but as the failure is directly
related to the pylab switch of ipython, I thought I try it here first:
On OSX I have trouble with using the pylab switch for ipython after I copied
the
On 2010-04-13 11:13 AM, K. -Michael Aye wrote:
On 2010-04-13 10:18 AM, K. -Michael Aye wrote:
Dear all,
maybe this should go to the Enthought list, but as the failure is directly
related to the pylab switch of ipython, I thought I try it here first:
On OSX I have trouble with using the
On 2010-04-13 18:13:40 +0200, K. -Michael Aye said:
On 2010-04-13 10:18 AM, K. -Michael Aye wrote:
Dear all,
maybe this should go to the Enthought list, but as the failure is
directly related to the pylab switch of ipython, I thought I try it
here first:
On OSX I have trouble with
On 2010-04-13 16:55 PM, K.-Michael Aye wrote:
Trying Unison via the GMane NNTP now, but weird that nabble has your
last answer already for long time, whereas GMane still does not show
it. Does the NNTP pull the mailing lists on a low frequency.
The latency is variable, but it's been getting
Hi All,
I am trying to understand exactly what the -pylab option does when I
launch ipython -pylab - thought some folks here might know.
For example, after executing
ipython -pylab
I can type either
a = np.array([1.,10.])
OR
b = array([1.,10.])
are these both numpy arrays? And clearly,
On Tue, Mar 9, 2010 at 6:48 PM, Andre Walker-Loud walksl...@gmail.comwrote:
Hi All,
I am trying to understand exactly what the -pylab option does when I
launch ipython -pylab - thought some folks here might know.
For example, after executing
ipython -pylab
I can type either
a =
Ryan May wrote:
Put this in your ~/.ipython/ipythonrc:
pylab_import_all 0
I finally got around to doing this, and found:
# ===
# Deprecation note: you should look into modifying ipy_user_conf.py
(located
# in
On Mon, Jul 27, 2009 at 2:40 PM, Christopher Barker
chris.bar...@noaa.govwrote:
Ryan May wrote:
Put this in your ~/.ipython/ipythonrc:
pylab_import_all 0
I finally got around to doing this, and found:
# ===
#
On Wed, Jul 22, 2009 at 6:09 PM, Christopher Barker
chris.bar...@noaa.govwrote:
Hi folks,
Does anyone know if there is a way to use ipython with the advantages of
the -pylab option (separate gui thread, etc.), but without the whole
pylab namespace getting sucked in?
Put this in your
On Wed, Jul 22, 2009 at 8:04 PM, Ryan Mayrma...@gmail.com wrote:
On Wed, Jul 22, 2009 at 6:09 PM, Christopher Barker chris.bar...@noaa.gov
wrote:
Hi folks,
Does anyone know if there is a way to use ipython with the advantages of
the -pylab option (separate gui thread, etc.), but without the
On Wed, Jul 22, 2009 at 8:34 PM, John Hunter jdh2...@gmail.com wrote:
On Wed, Jul 22, 2009 at 8:04 PM, Ryan Mayrma...@gmail.com wrote:
On Wed, Jul 22, 2009 at 6:09 PM, Christopher Barker
chris.bar...@noaa.gov
wrote:
Hi folks,
Does anyone know if there is a way to use ipython with
On Wed, Jul 22, 2009 at 8:50 PM, Ryan Mayrma...@gmail.com wrote:
I'm willing to. However, I just noticed that with just the pylab_import_all
0, you get the import numpy as np and import matplotlib.pyplot as plt
automatically. Also, nicely, these don't show up when you type 'whos'. This
is
Hello,
I have some trouble with ipython and matplotlib. I create a figure in
one of my functions that I call from ipython. The first time it runs
fine and I can use the figure interactively (selecting/ deselcting
points and so on). The second time I run it, the code doesnt stop but
Can you attach the traceback?
Cheers,
Mike
Wolfgang Kerzendorf wrote:
Hello,
I have some trouble with ipython and matplotlib. I create a figure in
one of my functions that I call from ipython. The first time it runs
fine and I can use the figure interactively (selecting/ deselcting
Hi all,
sorry for the quick cross-post, but I know that many mpl users rely on
the ipython -pylab support for interactive work.
This is a call for testing from current SVN of anyone who uses ipython
with the GUI thread support, whether via -pylab or directly via one of
the -Xthread options.
For
I had a problem yesterday running a script in interactive mode in
ipython -pylab using the gtk backend. In the script there was some
expensive computation, and I wanted to break out of it by hitting
CTRL-C. Because of the nastiness of signal handling across threads,
this isn't possible, though
31 matches
Mail list logo
