python2 vs. python3 matplotlib different results

Autoscaling is producing a different result on p2 vs p3. Maybe a missed
N/M -> N//M ??

[nbecker@...1160... dvbs2x_iter]$ rpm -q python-matplotlib
python-matplotlib-1.2.0-14.fc19.x86_64
[nbecker@...1160... dvbs2x_iter]$ rpm -q python3-matplotlib
python3-matplotlib-1.2.0-14.fc19.x86_64

Cheers!
Ben Root

···

On Wed, Aug 28, 2013 at 10:45 AM, Neal Becker <ndbecker2@...149...> wrote:

Autoscaling is producing a different result on p2 vs p3. Maybe a missed
N/M -> N//M ??

[nbecker@...1160... dvbs2x_iter]$ rpm -q python-matplotlib
python-matplotlib-1.2.0-14.fc19.x86_64
[nbecker@...1160... dvbs2x_iter]$ rpm -q python3-matplotlib
python3-matplotlib-1.2.0-14.fc19.x86_64

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 Wed, Aug 28, 2013 at 10:45 AM,
Neal Becker <ndbecker2@…149…>
wrote:

              Autoscaling

is producing a different result on p2 vs p3. Maybe a
missed

              N/M -> N//M ??



              [nbecker@...1160... dvbs2x_iter]$ rpm -q

python-matplotlib

              python-matplotlib-1.2.0-14.fc19.x86_64

              [nbecker@...1160... dvbs2x_iter]$ rpm -q

python3-matplotlib

              python3-matplotlib-1.2.0-14.fc19.x86_64

Cheers!

Ben Root