MNT: Update feedstock recipe for modern noarch python

[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
• Use a Jinja2 set statement for the python_min to allow all the build metadata to be contained in the recipe/meta.yaml and override the global python_min with packaging's python_min of 3.8.
• Remove --no-deps as the build tool (e.g. conda-build, rattler-build) will specify all required pip install options.
  • c.f. Question: why is --no-deps --no-build-isolation set? conda/grayskull#582
• Use 'pypi.org'.
• Add @matthewfeickert and @ofek as feedstock maintainers.
  • c.f. packaging v24.2 #31 (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.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ No valid build backend found for Python recipe for package packaging using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[matthewfeickert]

The recipe should pass the linter, but the reason for the linter is complaining will be fixed by conda-forge/conda-smithy#2132.

[matthewfeickert]

@conda-forge/packaging @conda-forge/core this is ready for review. c.f. #31 (comment)

@ofek, please comment or 👍 if you accept being added as a feedstock maintainer.

[ofek]

Looks good to me and I accept.

[h-vetinari]

Thanks for stepping up! @conda-forge/packaging, please let us know if you are OK with some additional support. Otherwise I will merge in ~1 week.

[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 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/11820030822.}

[matthewfeickert]

Gentle ping to @jakirkham and @nicoddemus.

[matthewfeickert]

@conda-forge-admin, please rerender

[matthewfeickert]

@conda-forge/packaging @conda-forge/core now that we have approval, I've rebased and squashed and rerendered, and this is ready for merge.

[jakirkham]

Thanks all! 🙏