Conda dependencies from multiple channels

[rbiswas4]

I was looking at the travis yml file and noticed that this added conda_deps and pip_deps to the script iteself. That is quite cool as a one liner instead of a script.

• Is there an easy way to handle multiple conda channels in such dependencies?
• I had heard that at some point conda install would default to pip install for packages not found in conda. I am guessing that has not yet happened in the conda releases yet?

[arokem]

On Wed, Jun 28, 2017 at 3:03 PM, rbiswas4 ***@***.***> wrote: I was looking at the travis yml file and noticed that this added conda_deps and pip_deps to the script iteself. That is quite cool as a one liner instead of a script.

I am not sure I understand: should we change anything about the way this is currently done? Are you suggesting the installation of dependencies should be in the `script` block (below)?

- Is there an easy way to handle multiple conda channels in such dependencies? I think so. Notice that this currently adds conda-forge as a channel. I

believe that you can have different lines with: conda install -c channel1 dependency1 conda install -c channel2 dependency2

- I had heard that at some point conda install would default to pip install for packages not found in conda. I am guessing that has not yet happened in the conda releases yet? Sorry - I don't know anything about that. Do you have a link to any

documentation about this?

…

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#66>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHPNmFJEbUl0vVF90MZv7U-uuhkhNkaks5sIs3PgaJpZM4OIl5U> .