Fixing miniconda path in .travis.xml and updating helpers

[bsipocz]

Miniconda's default prefix changed recently causing all travis builds failing.

And while I was at it I've updated the helpers to the latest one.

[bsipocz]

@astrofrog - Do you want to use ci-helpers here, too? If yes I can update this PR.

[astrofrog]

@bsipocz - yes, that would be great, thanks!

[astrofrog]

@bsipocz - can you change this to stable?

[bsipocz]

sure.

On 18 January 2016 at 14:21, Thomas Robitaille notifications@github.com
wrote:

In .travis.yml
#180 (comment):

env:
global:
# The following versions are the 'default' for tests, unless
# overidden underneath. They are defined here in order to save having
# to repeat them for all configurations.

•    - NUMPY_VERSION=1.9
  

•    - NUMPY_VERSION=1.10
  

@bsipocz https://github.com/bsipocz - can you change this to stable?

—
Reply to this email directly or view it on GitHub
https://github.com/astrofrog/wcsaxes/pull/180/files#r50003030.

[bsipocz]

Some of the tests fail with the OrderedDict issue, and many fail with pytest-mpl. I guess we should fix mpl version to 1.4.3 to get them pass?

[astrofrog]

@bsipocz - yes, that might make sense for now. I can look at the pytest-mpl issues today. Can you update the OrderedDict imports?

[bsipocz]

It's already in #184

[bsipocz]

Do you want appveyor, too?

[astrofrog]

@bsipocz - I'm not sure if the image testing will work on Windows, so maybe we can do that in another PR once one of us has time

[bsipocz]

Ohh, sure, I've already forgot about the image testing issues. That case it should be definitely a new PR.

[bsipocz]

@astrofrog - now I've rebased this on #184, so it should pass and be ready for review.

[astrofrog]

@bsipocz - I think the remaining issue is because you need to change the language to c and set PYTHON_VERSION manually (like we do in the core package). Otherwise it tries to get a built-in 3.5, which doesn't seem to work.

[bsipocz]

@astrofrog - Could you please restart that build? It didn't fail before, and the last commit didn't touch any 3.5 related stuff so I think it's very probably just a random fail.

[astrofrog]

You can actually just remove Python 2.6 support and include only the import from collections

[bsipocz]

OK, sounds good.

[astrofrog]

Thank you very much @bsipocz! :)