MNT: Use noarch python {{ python_min }} variable

[matthewfeickert]

• 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
  • c.f. [bot-automerge] uproot v5.4.2 #160 (comment)
• Add recipe/conda_build_config.yaml to override the global python_min with uproot's
  python_min of 3.8.
• Bump build number.
• MNT: Re-rendered with conda-build 24.9.0, conda-smithy 3.44.2, and conda-forge-pinning 2024.11.07.16.38.57

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.

* 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
* Add recipe/conda_build_config.yaml to override the global python_min with uproot's
  python_min of 3.8.
* Bump build number.
* MNT: Re-rendered with conda-build 24.9.0, conda-smithy 3.44.2, and conda-forge-pinning 2024.11.07.16.38.57

[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.
I do have some suggestions for making it better though...

For recipe/meta.yaml:

• noarch: python recipes should almost always follow the syntax in our documentation. For the host section of the recipe, you should almost always use python {{ python_min }} for the python entry. For the run section of the recipe, you should almost always use python >={{ python_min }} for the python entry. For the test.requires section of the recipe, you should almost always use python {{ python_min }} for the python entry. You may need to override the python_min variable in the conda_build_config.yaml/variants.yaml if the package requires a newer Python version than the currently supported minimum version on conda-forge.

[conda-forge-admin]

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

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11733592006.}

[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]

@conda-forge-admin, please rerender

[matthewfeickert]

You may need to override the python_min variable in the conda_build_config.yaml/variants.yaml if the package requires a newer Python version than the currently supported minimum version on conda-forge.

Okay, so I now need to figure out how to override python_min as to be '3.8'.

[matthewfeickert]

@beckermr @chrisburr @jakirkham This isn't very clear from https://docs.conda.io/projects/conda-build/en/latest/resources/variants.html#general-pinning-examples (as there's nothing on this in https://conda-forge.org/docs/). Do we need to create a recipe/conda_build_config.yaml that is just

python_min:
- '3.8'

or do we need to include all possible Python information in it, essentially duplicating all information in .ci_support/linux_64_.yaml

pin_run_as_build:
  python:
    min_pin: x.x
    max_pin: x.x
python:
- 3.12.* *_cpython
python_min:
- '3.8'

?

[matthewfeickert]

cc @dopplershift given his participation (and shared concerns on supporting older Pythons) in conda-forge/conda-forge.github.io#2210. Ryan, maybe you have insight here as to how this works?

[beckermr]

Put the value you want in a conda-build config in the feedstock and then rerender.

[beckermr]

Hopefully that works. If not, we can try other things.

[matthewfeickert]

Thanks very much @beckermr. That indeed does work. 👍

If I find time this evening I will open and Issue and PR to make things a bit more explicit for people who have only been doing this for a few years like me.

[jakirkham]

Improvements to the docs would certainly be welcome 🙂

Writing good docs seems to be one of the hardest problems in open source. So we welcome all the help we can get 😅

[matthewfeickert]

It's hard, and also the conda-forge team has an nearly impossible task of covering a huge landscape of complicated infrastructure (that still amazingly "just works"!).

Given that I'm trying to unbreak some Scikit-HEP related builts that might not happen tonight, but my goal is to open up a PR in the next 24 hours to iterate with you all on. 👍

[matthewfeickert]

Okay, so closer to 96 hours, but: conda-forge/conda-forge.github.io#2370

[matthewfeickert]

@conda-forge-admin, please rerender