Thread: [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

On Wed, Aug 28, 2013 at 10:45 AM, Neal Becker <ndb...@gm...> 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-matplotlib
> python3-matplotlib-1.2.0-14.fc19.x86_64
>
>
Cheers!
Ben Root

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 <ndb...@gm... 
> <mailto:ndb...@gm...>> 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-matplotlib
> python3-matplotlib-1.2.0-14.fc19.x86_64
>
>
> Cheers!
> Ben Root
>
>
> ------------------------------------------------------------------------------
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel