pin numpy >=2.1 and python >=3.10

[kmuehlbauer]

closes #13

Not sure how to fix the _0 build, but maybe this is just a change in the metadata of the package.

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.

[kmuehlbauer]

@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.
• PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

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

[kmuehlbauer]

@conda-forge/array-api-strict @conda-forge/core Please check this PR, #13 will affect any automated CI where numpy <2.1 is installed.

[xhochy]

What's the reason to ping core here? Please keep it with feedstock maintainers and only ping core if they don't respond.

[kmuehlbauer]

Thanks @xhochy for responding, and sorry for pinging core. This affects my day work, but I'll work around for now. I'll wait for the maintainers to respond.

[rgommers]

Thanks @kmuehlbauer! The changes here are correct, however we also need python >=3.10 rather than >=3.9 now. I'll add that as well.

[kmuehlbauer]

Thanks for taking care that quickly @rgommers!

[jakirkham]

These version constraint changes could be picked automatically during version updates if Grayskull were enabled here

More details on how to do this in issue: #9