Require setuptools<82

[jdblischak]

Checklist

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

---

Closes #1

• setuptools 82 removed pkg_resources
• This is breaking packages that import xarray-schema (eg ImportError: pkg_resources missing when importing spatialdata (setuptools ≥ 82) scverse/spatialdata#1065)
• xarray-schema runs import pkg_resources in its __init__.py, so this needs to be a runtime requirement too
• This is being worked on upstream too (Update deprecated pkg_resources usage xarray-contrib/xarray-schema#193, Remove deprecated pkg_resources xarray-contrib/xarray-schema#194)
• I also work on repodata patch to fix this for the conda-forge ecosystem
• I also bumped numpy to >=1.21 to match the upstream requirements

[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 host section of the recipe, you should usually use the pin python {{ python_min }} for the python entry.
  • For the run section of the recipe, you should usually use the pin python >={{ python_min }} for the python entry.
  • For the test.requires section of the recipe, you should usually use the pin 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).
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

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

[h-vetinari]

setuptools 82 deprecated pkg_resources

"deprecated" -> "removed", which makes a world of difference.

Would be nice to address the CFEP-25 warnings.

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

[h-vetinari]

Given the current breakage, let's merge this. Thanks for the fix!