From 7f5404d8e996dbb0d302eba793fcedde0562aa30 Mon Sep 17 00:00:00 2001 From: Geoffrey Date: Wed, 22 Jul 2020 19:21:41 +0200 Subject: [PATCH] Fix bug # More detailed explanatory text, if necessary. Wrap it to about 72 # characters or so. In some contexts, the first line is treated as the # subject of the commit and the rest of the text as the body. The # blank line separating the summary from the body is critical (unless # you omit the body entirely); various tools like `log`, `shortlog` # and `rebase` can get confused if you run the two together. # Explain the problem that this commit is solving. Focus on why you # are making this change as opposed to how (the code explains that). # Are there side effects or other unintuitive consequences of this # change? Here's the place to explain them. # Further paragraphs come after blank lines. # - Bullet points are okay, too # - Typically a hyphen or asterisk is used for the bullet, preceded # by a single space, with blank lines in between, but conventions # vary here # If you use an issue tracker, put references to them at the bottom, # like this: # Resolves: #123 # See also: #456, #789 --- .travis.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 8935905..bef41a4 100644 --- a/.travis.yml +++ b/.travis.yml @@ -11,7 +11,7 @@ before_install: - export PATH="$HOME/miniconda/bin:$PATH" - conda update --yes conda - conda create --yes --name testenv python=$TRAVIS_PYTHON_VERSION - - conda activate testenv + - source activate testenv install: - python setup.py install - conda install --yes pytest scikit-learn