Unpin Python in tests

[xhochy]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• 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.

[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 usually follow the syntax in our documentation for specifying the Python version.
  • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

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

[rgommers]

Question, since I had a need to ignore the linter elsewhere already: is there a way to tell the linter "this is intended"? Something like the # type: ignore for Mypy or # noqa: for Ruff?

[h-vetinari]

Nothing structured like that, because smithy is just string-parsing, mainly (things should get easier with the v1 recipe).

However, Isuru recently introduced a mechanism opt out of certain lints, which could be extended to python_min

[h-vetinari]

See conda-forge/conda-smithy#2170