Skip to content

Test against astropy dev - #172

Closed
SolarDrew wants to merge 2 commits into
PlasmaPy:masterfrom
SolarDrew:test-improvement
Closed

SolarDrew wants to merge 2 commits into
PlasmaPy:masterfrom
SolarDrew:test-improvement

Conversation

@SolarDrew

Copy link
Copy Markdown
Contributor

Added a parameter in .travis.yml so that Travis will build and test against the development version of astropy as well as the released version.

@StanczakDominik

Copy link
Copy Markdown
Member

As it stands we're downloading conda 4.3.30, downgrading it to 4.3.27, installing three separate bunches of packages via pip only for Astropy to scream about ImportError: Numpy version 1.10.0 or later must be installed to use Astropy. I have no idea what's happening here and why, but it doesn't quite look good.

Comment thread .travis.yml

matrix:
include:
- env: ASTROPY_VERSION='dev'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm guessing you need another matrix entry for non-dev astropy?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth explicitly selecting python 3.6 here too

@StanczakDominik
StanczakDominik force-pushed the master branch 4 times, most recently from 02e758d to 749a6bd Compare April 29, 2018 16:04
@namurphy

namurphy commented Oct 2, 2018

Copy link
Copy Markdown
Member

I'm going to tentatively close this PR since we haven't worked on it in a long time, but we can re-open it later if we want to finish figuring out how to test against astropy dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants