Ken Odegard

Duplicate of https://github.com/conda/conda/issues/13015

@jaimergp beat me to it, yes it's the pre-parser and we need to implement `--` support to resolve this

Beware the history of `conda env` when thinking about `conda plugins`

@adhadse Thanks for raising this. We've been contemplating for a while on how to better support the shells currently supported by conda in addition to new shells. I've started to...

`conda env config vars set NAME=value` will update `conda-meta/state` for the active environment: ``` {"env_vars": {"NAME": "value"}} ``` `conda env config vars unset NAME` on the other hand is not...

libmamba raises a `RuntimeError` and correctly warns about an unmanageable package (albeit not very politely)

> 1. What are the purposes of activation, i.e., what should the activation procedure be able to do? Activation boils down to modifying your `%PATH%` (and setting some additional environment...

@conda-bot check

@Tobias-Fischer thanks for checking in, we're still working to resolve the unrelated test failures caused by upstream deprecations, once we untangle that we'll get this moving again

The tests are failing because setting the field type to `bool` changes the default value for `build/activate_in_script` to `False`. Without setting the field type the default value is `None` which...