Closed davidcaron closed 4 years ago
Sounds tricky. Is there another option in conda we could use? We might not remember this comment.
Well... maybe we should use conda-forge only in this cookiecutter. (uncommenting it in the environement.yml file) and set .travis.yml to install python from conda-forge also. I think this is what most projects probably do right now.
Well... maybe we should use conda-forge only in this cookiecutter. (uncommenting it in the environement.yml file) and set .travis.yml to install python from conda-forge also. I think this is what most projects probably do right now.
Ok. I agree. Would you like to update this PR with this change?
@cehbrecht If you want, I can make these changes and add them in here. Your call.
@cehbrecht If you want, I can make these changes and add them in here. Your call.
@Zeitsperre go ahead :) Thanks for taking it up ...
Overview
I just wanted to add a note in
.travis.yml
for a bug that bit us in finch that was a bit hard to find. https://github.com/bird-house/finch/pull/63When our packages come from conda-forge, some packages (notably GDAL) will get installed with the channel where python itself came from. So if python was installed from defaults, installing GDAL with
conda install -c conda-forge GDAL
will still install it from defaults.