Ben Mares

Given things like this and #196, how would you feel about by default regenerating the lockfile from scratch. I don't have experience with other lockfile systems, but I find it...

Hi, I'm having trouble reproducing this. What's your conda-lock version? BTW, a few minor suggestions: 1. You may have default channels configured in your `~/.condarc`, but to ensure portability, it's...

Last time I tried adding something as a `dev` and `main` dep it led to it not being installed in `main`. That's why we need to turn `category: str` into...

> I would recommend not including conda-lock in your lockfile itself. Thats a rather weird antipattern. Yes, but it's normal to have `conda-lock` in `dev-environment.yml` right? (Especially if one uses...

Regarding `categories:`, I proposed a change to the lockfile format in https://github.com/mamba-org/mamba/issues/1209#issuecomment-1236086736. The response was positive, but there doesn't seem to be any movement yet towards an implementation.

Regarding `categories` I just had a rough idea how we might be able to move the concept forward from purely the conda-lock side, posted as #278. I'm not sure if...

Hi @Ben-Habermeyer, in practice I've usually managed to work around the issue by ensuring that main dependencies are never repeated as dev dependencies and then occasionally adding any missing transitive...

> I will also take a look at pixi as you suggested. For the time being do you suggest following #273 as the root issue when a fix may be...

Sure, just define different categories for the two environment files. However there is currently a major bug #278, but there is a fix in the pipeline.

Micromamba accepts `--category` as you describe. `conda-lock install` is lagging behind here. This should be implemented.