Isuru Fernando

> I'm not clear on build_to_build and host_to_host - why not just add these as dependencies? Because the constraints might not be strict. For eg: build 1 of `B=1.*` might...

You have to use `_` instead of `-` in `recipe/conda_build_config.yaml`. This is documented in https://docs.conda.io/projects/conda-build/en/latest/resources/variants.html

> none of their examples involve pinning packages that have dashes in the name, and they don’t mention that case. There's an example with `r-base`.

Can you send a PR to the docs with your suggested wording? Also, please tone down your language.

> I apologize for my tone Thanks > but I’m a bit frustrated by yours – your two messages basically said I was an idiot for not knowing the solution,...

Should we fix the name for python in the shebang of entry-points in this CEP or a separate one? Currently there's a `python3.13t->python3.13` symlink

A bit of context about the python executable name. On Unix, CPython (upstream and conda) has python3.13 for freethreading and default builds. For freethreading python3.13 is a symlink to python...

I don't think we should introduce any other noarch types. `noarch: generic` is enough for most use-cases and we should just use a version independent path for other languages. For...

> Certainly, one interpretation of noarch-Python is that it's historic debt. But eliminating it would require patching the default path search behavior of python; and there is version-dependent byte compilation...

That's the wrong thing to do. We want an explicit equal bounds in `host` to make sure the package actually works/