Marius van Niekerk
Marius van Niekerk
In general package removal is a very complex thing. You're better of just deleting the lock file and regenerating entirely.
`LocalCluster` very much does support `adapt` as shown by https://gist.github.com/mariusvniekerk/edeefd93b17a7ae01472e1818512ac55
The new format IS supported natively in micromamba though
So ensureconda (https://github.com/conda-incubator/ensureconda) is a tiny little tool that like pip ensures that a conda (or conda-like) is around. It has some built in ways to install the standalone conda...
We can certainly integrate some of the features from ensureconda into setup-miniconda if it makes sense
Yeah main difference is mostly the micromamba standalone installation doesn't need conda at all, so you save a conda solve for mamba.
Configuration for querier.frontend_worker.grpc_client_config.max_recv_msg_size doesn't seem to work?
probably not particularly hard, since it is really just a `conda list --explicit -p {some_prefix}/-n {some name}`. The lock generated from this would by necessity be confined to the source...
Due to the fact that conda-lock supports multiple output formats it relies in a rather large part on the extension used in specifying the output format. If you want to...
probably in keeping with the structure of pep621 pyproject-toml files ``` [tool.conda-lock.optional-dependencies] dev = ["git"] someothercategory = ["another dep"] ```