Unfortunately, this is breaking some tests - see https://travis-ci.org/github/python-quantities/python-quantities/builds/681112615

(I don't know why the Travis results aren't showing up here in the PR)

I just looked at one and it already looks pretty serious: https://travis-ci.org/github/python-quantities/python-quantities/jobs/681112616

I'm not sure how else could we fix this issue then.

FAIL: test_std (quantities.tests.test_methods.TestQuantityMethods)

Traceback (most recent call last):
File "/home/travis/build/python-quantities/python-quantities/quantities/tests/test_methods.py", line 261, in test_std
self.methodWithOut('std', 1.1180339887498949 * pq.m)
File "/home/travis/build/python-quantities/python-quantities/quantities/tests/test_methods.py", line 128, in methodWithOut
result
File "/home/travis/build/python-quantities/python-quantities/quantities/tests/common.py", line 34, in assertQuantityEqual
% (delta, q1.magnitude, q2.magnitude, msg)
AssertionError: Magnitudes differ by more than 1e-05 (1.25 vs 1.11803398875)

Hi @apdavison ,
Is it possible to add a test for numpy 1.15.1 and Python 2.7.15. That's what we are using and have deployed a custom build with this change already. If this test fails, I would need to revert to the regular quantities package.

@vrindger I've added a "Python 2.7 + Numpy 1.15.1" entry to the test matrix (we actually get Python Python 2.7.17 not 2.7.15, but I don't believe that will make any difference).

This combination passes on the master branch. I think you'll have to add a commit to this PR to trigger the tests to run again with the new Numpy 1.15.1 test.

Thanks @apdavison

I triggered a fresh set of Travis tests with a non-change commit.
I see that there was just one test that failed and it's a backward compatibility test? This does not look very serious to me. What are your thoughts?
https://travis-ci.org/github/python-quantities/python-quantities/jobs/684481440

ERROR: test_backward_compat (quantities.tests.test_persistence.TestPersistence)
A few pickles collected before fixing #113 just to make sure we remain backwards compatible.

@vrindger sorry we didn't get this merged. We've now dropped support for Python 2.7, so I'm closing this PR now.