This was using pdfpages (if that matters)
Traceback (most recent call last):
File ./plot_stuff2.py, line 326, in module
the_plot.finish (args, opt, time, res)
File ./plot_stuff2.py, line 145, in finish
self.pdf.savefig (self.fig)
File /home/nbecker/.local/lib/python2.7/site-
This isn't a matplotlib bug. Somehow, a py2.x version of nose got into your
python3.3 site-packages. Try clearing that out first. Of course, it might
still be possible that we are somehow forcing the wrong nose to be
installed...
Can you provide a code example to reproduce this. I suspect that recent
work on path effects might be to blame here. Also, exactly which version of
matplotlib and numpy were you using? The assert was placed there about a
year ago IIRC to deal with a short-lived numpy bug.
Can you provide a standalone example to reproduce? The multipage_pdf.py
example works fine with xkcd switched on.
Mike
On 10/23/2013 08:01 AM, Neal Becker wrote:
This was using pdfpages (if that matters)
Traceback (most recent call last):
File ./plot_stuff2.py, line 326, in module
This is really strange. It d/l 1.3.1, but then builds installs 1.3.0???
python3-pip install --user --up --no-deps matplotlib
Downloading/unpacking matplotlib from
https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.1/matplotlib-1.3.1.tar.gz
Running setup.py egg_info
OK, this seems to be a pip caching bug. After rm -rf /tmp/pip*, it installed
correctly
Neal Becker wrote:
This is really strange. It d/l 1.3.1, but then builds installs 1.3.0???
python3-pip install --user --up --no-deps matplotlib
Downloading/unpacking matplotlib from
Benjamin Root wrote:
Can you provide a code example to reproduce this. I suspect that recent
work on path effects might be to blame here. Also, exactly which version of
matplotlib and numpy were you using? The assert was placed there about a
year ago IIRC to deal with a short-lived numpy bug.
On 10/23/2013 09:51 AM, Neal Becker wrote:
Benjamin Root wrote:
Can you provide a code example to reproduce this. I suspect that recent
work on path effects might be to blame here. Also, exactly which version of
matplotlib and numpy were you using? The assert was placed there about a
year
In article
cah6pt5owd7habzoerz7itbw+br80uy0z6+mpaetqemskm9v...@mail.gmail.com,
Matthew Brett matthew.br...@gmail.com
wrote:
Hi Chris,
On Tue, Oct 22, 2013 at 9:03 AM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
Are there recent binaries for OS-X anywhere? There don't seem
Hi,
On Wed, Oct 23, 2013 at 11:30 AM, Russell E. Owen ro...@uw.edu wrote:
In article
cah6pt5owd7habzoerz7itbw+br80uy0z6+mpaetqemskm9v...@mail.gmail.com,
Matthew Brett matthew.br...@gmail.com
wrote:
Hi Chris,
On Tue, Oct 22, 2013 at 9:03 AM, Chris Barker - NOAA Federal
On 10/23/2013 02:41 PM, Matthew Brett wrote:
Hi,
On Wed, Oct 23, 2013 at 11:30 AM, Russell E. Owen ro...@uw.edu wrote:
In article
cah6pt5owd7habzoerz7itbw+br80uy0z6+mpaetqemskm9v...@mail.gmail.com,
Matthew Brett matthew.br...@gmail.com
wrote:
Hi Chris,
On Tue, Oct 22, 2013 at 9:03
On Wed, Oct 23, 2013 at 11:30 AM, Russell E. Owen ro...@uw.edu wrote:
The last ones I got from you worked very well: just a few test failures
and the current one seems to be doing about the same.
worked well for me too (something odd with wx back end re-rendering,
but I doubt that's a Mac build
Hi,
On Wed, Oct 23, 2013 at 12:37 PM, Chris Barker chris.bar...@noaa.gov wrote:
On Wed, Oct 23, 2013 at 11:30 AM, Russell E. Owen ro...@uw.edu wrote:
The last ones I got from you worked very well: just a few test failures
and the current one seems to be doing about the same.
worked well for
13 matches
Mail list logo
