Jesko Wagner

That's neat! So what should be the basic advice for conda users that have one or more of the problems listed in #11800? That is, do we want to move...

I see that @jezdez and @dholth have been assigned now. I would like to wait with changes to hear their view on preferred implementations, because ultimately @Anaconda will have to...

@jezdez and @dholth, could I please get an update about your preferred implementation? I would like to move forward with this PR as it's a feature that I could use...

@pgramme Fair points. I think for many users `--from-history` is the starting point to derive a slim `yaml` that they can share with others. The issue with a "default" `conda...

[The Carpentries](https://carpentries-incubator.github.io/introduction-to-conda-for-data-scientists/04-sharing-environments/index.html) similarly recommend `conda env export --from-history` for device-independent environment definitions. When teaching this course I often get questions about how to include pip packages and fully versioned definitions....

I agree that the proposed changes remain useful. However, note that I have not implemented the all changes because it is unclear what flags/changes would be deemed acceptable by @anaconda,...

Thanks a lot for your fast response! Indeed what I am looking for is similar to existing functionality. Specifically, I would like to keep base coverage per region in the...

Thanks for the update! Since (as far as I can tell) `bwtool` is not under active development I would not be surprised to hear of any bugs in its output....

Just in case access to the paper would help: my institution provides access, see this [pdf](https://github.com/CellProfiler/CellProfiler/files/11982213/Power_Vectors__An_Application_of_Fourier_Analysis.19.pdf) for the paper.

Hi David, While possible it is (I think) not best practice, because you can have ambiguous environment names this way. That is, one could end up accidentally creating two environments...