Marius van Niekerk
Marius van Niekerk
In general `conda-lock install` should not augment existing environments, but should replace them instead. As for the large indexing load on pycharm, that is sadly unavoidable.
Which versions of conda/ mamba are you using in conjunction with conda-lock?
For complex dependencies like geopandas I would *strongly* recommend using mamba
You can probably make use of a temporary `$CONDARC` that allows flexible channel priority. For the most part, if you don't have the defaults channel at all strict channel priority...
Yeah this is more a result of how `conda` works. If you have a `conda` executable in an environment it effectively becomes a root environment as well. I would recommend...
The other thing that may work is to have a configuration like ``` envs_dirs: - /home/nelius/miniconda3/envs/ ``` in your `~/.condarc`
you might be able to get this to work by passing the path to conda explicitly ```shell $ /home/nelius/miniconda3/bin/conda run --prefix /home/nelius/miniconda3/envs/mlops \ conda-lock install --dev \ --prefix /home/nelius/miniconda3/envs/mlops mlops.conda-lock.yml...
@Titus-von-Koeller if you feel up to it i think an excellent PR would be for a FAQ style document for more complex edge cases like this. Perfectly fine if its...
We should probably make this git ignored
When accessing a private channel using conda lock the environment variable form as described in https://conda-incubator.github.io/conda-lock/authenticated_channels/ is the recommended approach. What does your condarc look like? Additionally versions for python,...