Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keeping order of installs #124

Merged
merged 2 commits into from
Nov 4, 2016
Merged

Conversation

bsipocz
Copy link
Member

@bsipocz bsipocz commented Aug 8, 2016

This is an attempt to address #123.
Not sure how it can be tested, but e.g. in the prerelease travis test, scipy now shouldn't be installed even though it's listed in CONDA_DEPENDENCIES.

If this works, I'll add more commits to deal with the astropy step.

# We then install Numpy itself at the bottom of this script
export CONDA_INSTALL="conda install $QUIET python=$PYTHON_VERSION"
elif [[ $NUMPY_VERSION == stable ]]; then
conda install $QUIET numpy=$LATEST_NUMPY_STABLE
conda install $QUIET --no-pin numpy=$LATEST_NUMPY_STABLE
Copy link
Member

Choose a reason for hiding this comment

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

Will it not be the case that when installing the main dependencies later, there will still be the issue that the pin file can contain numpy stable*?

Copy link
Member Author

Choose a reason for hiding this comment

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

yes, probably you're right, I'll look at this again.

Copy link
Member Author

Choose a reason for hiding this comment

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

No, numpy isn't listed in the pinfile, e.g. for a NUMPY_VERSION=stable CONDA_DEPENDENCIES='jinja2=2.8' build, the pinfile contains only jinja:

++++cat /home/travis/miniconda/envs/test/conda-meta/pinned

jinja2  2.8*

Copy link
Member Author

Choose a reason for hiding this comment

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

Do you think it's better to pin down the numpy version, too?

@bsipocz
Copy link
Member Author

bsipocz commented Nov 4, 2016

I'm merging this now, if there is a problem coming up we can still pin the numpy version, too.

@bsipocz bsipocz merged commit b28cd36 into astropy:master Nov 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants