Use conda 4.4+-style install for Travis-CI (conda activate, ...) #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch causes Travis to install and use miniconda in the conda 4.4 way:
-running conda.sh as a shell script instead of adding $HOME/miniconda3/bin to the path
-activating with
conda activate <env>This style of installation and use would seem to be the future. However I'm not sure that we shouldn't be testing both methods, since the miniconda installer and instructions at conda.io still tell the user to add the base bin directory to their path.
Also, I'm not familiar with conda installation on windows, so this PR doesn't touch the AppVeyor stuff.