Re: [matplotlib-devel] python2 vs. python3 matplotlib different results

You provide a single standalone example to reproduce this. Most of our files have |from __future__ import division|, so I'm not entirely sure what could be going on... Mike On 08/28/2013 11:56 AM, Benjamin Root wrote: On Wed, Aug 28, 2013 at 10:45 AM, Neal Becker

Re: [matplotlib-devel] python2 vs. python3 matplotlib different results

On Wed, Aug 28, 2013 at 10:45 AM, Neal Becker wrote: > Autoscaling is producing a different result on p2 vs p3. Maybe a missed > N/M -> N//M ?? > > [nbecker@nbecker7 dvbs2x_iter]$ rpm -q python-matplotlib > python-matplotlib-1.2.0-14.fc19.x86_64 > [nbecker@nbecker7 dvbs2x_iter]$ rpm -q python3-m

Re: [matplotlib-devel] cartopy: test suite questions

Thanks Andreas, > I couldn't find any test runner script / method. There is currently no "python setup.py tests" type runner (which would be welcomed), but the obvious test runner is to use "nose" - something like "nosetests cartopy" should do the trick. It'd also be very easy to put a function i

[matplotlib-devel] python2 vs. python3 matplotlib different results

Autoscaling is producing a different result on p2 vs p3. Maybe a missed N/M -> N//M ?? [nbecker@nbecker7 dvbs2x_iter]$ rpm -q python-matplotlib python-matplotlib-1.2.0-14.fc19.x86_64 [nbecker@nbecker7 dvbs2x_iter]$ rpm -q python3-matplotlib python3-matplotlib-1.2.0-14.fc19.x86_64 --