MNT: Use noarch python {{ python_min }} variable

[matthewfeickert]

• Move 'noarch: python` to top level build map.
  • Remove 'noarch: python' in output build maps as they seem to not do anything.
• Use 'python {{ python_min }}' syntax for the python requirements for noarch python recipes.
  • c.f. https://conda-forge.org/docs/maintainer/knowledge_base/#noarch-python
• Use a Jinja2 set statement for python_min to keep all the build metadata contained in the recipe/meta.yaml and override the global python_min with hist's python_min of 3.8.
• Add '--no-build-isolation' pip install flag given multiple outputs.
  • c.f. Question: why is --no-deps --no-build-isolation set? conda/grayskull#582 (comment)
• Bump build number.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• [N/A] Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[matthewfeickert]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[matthewfeickert]

@chrisburr as this is noarch why are there multiple Python builds happening and not just one?

[matthewfeickert]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

• Is the recipe/{meta.yaml,recipe.yaml} file valid?
• If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
• Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11958685116. Examine the logs at this URL for more detail.}

[matthewfeickert]

Hm. I guess {{ PYTHON }} won't work here, even though this is noarch: python. Maybe it is related to why there are multiple Python builds?

[matthewfeickert]

@conda-forge-admin, please rerender

[matthewfeickert]

I'm realizing now that this feedstock doesn't behave like noarch: python at all, and so this PR doesn't have the intended effect. We need to figure out why it isn't acting like noarch before we can merge.

[matthewfeickert]

@conda-forge-admin, please rerender

[matthewfeickert]

Thanks for the useful advice on the top level build map, @chrisburr!