jaimergp

We don't need it as a fix, but I'd say that this feature could be useful or at least the intent is more clear (perhaps with a different name). For...

If this goes forward, we should probably mark https://github.com/conda/conda/pull/14710 as experimental too, in a patch release.

I would assume that if a class is marked as experimental, all the methods inherit that status and hence do not need the prefix. Same goes with modules propagating it...

> If so doesn't that just mean that experimental is a different term for "private"? We don't have private anything, sadly. In a way it's a bit like that, but...

> Could we mimic the same pattern and have `@experimental`, experimental.constant and experimental.topic(...) etc? My concern with this is how we communicate to the developer that they should not really...

> I also don't understand why we can't just use the norms of Python programming by just prefacing things with underscores if you don't want people using it as a...

@conda/conda-maintainers, I'd like to reach consensus this week. We have merged some PRs already with `*EXPERIMENTAL*` disclaimers in the docstring. If that's sufficient for y'all, we can just document the...

Nah, wait, `MatchSpec.version` is defined but `MatchSpec.build` is never. That function should be using a default with `MatchSpec.get()`. That said, `MatchSpec.match()` is meant for `PackageRecords`, not other `MatchSpec` objects.

With pixi, importing the dependencies into a new toml and solving from scratch. macOS needs 24s to deploy `base`: ``` 2024-10-02T22:14:28.5022520Z Downloading pixi 0.30.0 2024-10-02T22:14:29.6253360Z + echo 'Creating environment' 2024-10-02T22:14:52.5630520Z...

See https://github.com/conda-forge/conda-forge.github.io/issues/2323#issuecomment-2389545402, @ruben-arts!