Thanks for the update.
On Tue, Jun 10, 2014 at 6:46 AM, John Evans
wrote:
> Just to close the loop on this, I figured out that the issue was minimally
> reproduced if the "import matplotlib.pyplot" line was replaced with just
> "import six". It was reported to the six package developers and th
Just to close the loop on this, I figured out that the issue was minimally
reproduced if the "import matplotlib.pyplot" line was replaced with just
"import six". It was reported to the six package developers and the
problem was resolved with the 1.7.0 release of six.
On Wed, Apr 16, 2014 at 12:3
Hmmm, it isn't the same, but I wonder if it is related to the oddities
around https://github.com/matplotlib/matplotlib/pull/2925 . What I mean is
that in that case, none of our unit tests caught the problem, even though
it should have. In your case, your unit tests is catching a similar
problem, bu
Helllo, I'm seeing a strange issue when running unittests on python3.3 and
python3.4 that somehow involves matplotlib. My code has a somewhat
complicated setup, but I think I've boiled the issue down to the following
reproduction steps
import unittest
import warnings
import matplotlib.pyplot
c
