Docs: update conda config key to mention build.tools.python

[humitos]

Make it clear that when using conda it's required to use build.tools.python with Conda or Mamba.

Closes #8595

---

📚 Documentation previews 📚

• User's documentation (docs): https://docs--10672.org.readthedocs.build/en/10672/

• Developer's documentation (dev): https://dev--10672.org.readthedocs.build/en/10672/

[humitos]

@st-bender would it be clearer with this change?

[st-bender]

@st-bender would it be clearer with this change?

Thanks.
Sounds good, maybe it would help to point out to set build.tools.python to one of the "<mini|mamba>forge-x.xx" tools, and that plain "3.x" does not include conda or mamba.

[humitos]

it would help to point out to set build.tools.python to one of the "<mini|mamba>forge-x.xx" tools, and that plain "3.x" does not include conda or mamba.

I'm not following here. What do you mean with "plan 3.x"? The example it's explicitly setting mambaforge-22.9.

[st-bender]

it would help to point out to set build.tools.python to one of the "<mini|mamba>forge-x.xx" tools, and that plain "3.x" does not include conda or mamba.

I'm not following here. What do you mean with "plan 3.x"? The example it's explicitly setting mambaforge-22.9.

It is now, thanks. What I was trying to point out is that setting build.tools.python to something like "3.9" or "3.11" or whatever does not work. It should be set to one that includes conda or mamba, and it is not at all obvious which ones include it and which ones do not. At least it was not for me, I had to consult stackoverflow, which made it clear that it has to be either miniconda or one of the mambaforge ones.