You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How would this feature be useful?
Minor addition for a common situation.
Describe the solution you'd like
What about having a channel= keyword argument for conda_install so that one could write channel="conda-forge" if selecting a channel? It would be a bit more natural than "--channel=conda-forge", I think, and likely is very common.
It is possible to set multiple channels - this is required for bioconda, for example. This could be an iterable, channel=["conda-forge", "bioconda"]. Maybe the keyword should be "channels" and always takes a list?
Describe alternatives you've considered
Leave as is.
The text was updated successfully, but these errors were encountered:
I think this is a good idea, I use conda a little bit and do sometimes run into difficulties with different channels. Having the flexibility to choose per session would be ideal and agree on the --channel inside the function being less natural.
How would this feature be useful?
Minor addition for a common situation.
Describe the solution you'd like
What about having a
channel=
keyword argument forconda_install
so that one could writechannel="conda-forge"
if selecting a channel? It would be a bit more natural than"--channel=conda-forge"
, I think, and likely is very common.It is possible to set multiple channels - this is required for bioconda, for example. This could be an iterable,
channel=["conda-forge", "bioconda"]
. Maybe the keyword should be "channels" and always takes a list?Describe alternatives you've considered
Leave as is.
The text was updated successfully, but these errors were encountered: