Switch py2.7 CI build to use conda-forge

[shoyer]

No description provided.

[ocefpaf]

@shoyer I am interested in help you investigate what is going on here as that will help us to keep the conda-forge stable. Can you please add conda config --set show_channel_urls true in the .travis.yml so we know where the packages are coming from? We just added scipy to conda-forge and I am afraid that might be the issue here.

Ping @jakirkham who added the scipy recipe to help investigate the issue 😬

[shoyer]

@ocefpaf looks like the previous build failed due to a lack of the "coveralls" package... just switched that back to pip, we'll see how that it goes.

[shoyer]

@ocefpaf Looks like it's the official Continuum build of SciPy that just started failing here (entirely coincidentally). I only switched to conda forge for our build with all optional dependencies py27-cdat+pynio. So I'm going to merge this for now and fix the minimal build later.

[jakirkham]

Please let me know if there is something actionable for me here. Looks like that is not the case. If that changes, please let me know.

[jakirkham]

Also, FYI we have python-coveralls currently. Though we don't have coveralls yet.

[ocefpaf]

@ocefpaf Looks like it's the official Continuum build of SciPy that just started failing here (entirely coincidentally). I only switched to conda forge for our build with all optional dependencies py27-cdat+pynio. So I'm going to merge this for now and fix the minimal build later.

Cool. I will take a look at adding coveralls once I get back in office. (Heading to PyCon. Will you be there @shoyer?)

[shoyer]

I just tried switching our other Python 2.7 build to use conda-forge and am still seeing the same issues with scipy:
#863

I'll try adding show_channels_urls to that build and we'll see what it reports.

@ocefpaf I'm not making it to PyCon (or scipy!) this year, but I hope you enjoy it. Portland is a great city!