Jannis Leidel

@kenodegard I think you might know best how this is triggered, I'm guessing because of the preparsing?

I do like the idea and think npx is a powerful, albeit niche, pattern. > in a special envs_dir we will set up for conda run -x exclusive use Not...

> Search current PATH for rever. Run if found. This represents a risk that non-conda variants are leaking into it, I would not do that. To further lower the barrier...

@travishathaway It's a good question, what you're describing is changing a core behavior, with a decade long history and strong opposition by the previous conda maintainer. As a former virtualenv...

I would add that there is also the discussion we had about a dedicated conda plugins subcommand that might be better suited for the plugin sepcific settings, e.g. `conda plugins...

See https://github.com/conda/conda/issues/11786#issuecomment-1234088871 for the mention, I think we have a user story in one of the Google docs as well

This seems to be using a pretty old version of conda, could you try to upgrade it again please? And also post the version information please?

`RuntimeError`s definitely also don't sounds super great. Should we add a new exception classes `UnmanagablePackage` or something that bubbles up a little more graceful?

Welcome to conda/conda :) Just thought it might be best to improve this here, where the solver options are hooked into the conda CLI.

FWIW, since this came up in #13445, we should make use of sphinx-autoapi's ability to use typehints [automatically to render return types](https://sphinx-autoapi.readthedocs.io/en/latest/how_to.html#how-to-include-type-annotations-as-types-in-rendered-docstrings) and not duplicate the information in the source...