astropy v6.1.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: disabled to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

• requests
• arm_pyart
• matplotlib
• dask
• pyinstaller
• pytest
• extension-helpers

Packages found in the meta.yaml but not found by source code inspection:

• importlib-metadata

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/8953961122 - please use this URL for debugging.}

[conda-forge-webservices]

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) and found it was in an excellent condition.

[mwcraig]

I'm not sure this will correctly build until conda-forge builds out support for numpy 2, since the build requirements now include numpy>=2.0.0rc1. I've updated the minimum python version and the minimum IERS data version for now.

[mwcraig]

@conda-forge-admin please rerender

[mwcraig]

@conda-forge-admin please rerender

[mwcraig]

Confirmed that numpy rc1 isn't working yet...

[astrofrog]

We could just patch pyproject in the recipe? Isn't this going to be an issue for all packages which are following the numpy recommendations btw?

[pllim]

Blocked by this?

• Packaging NumPy 2.0.0rc1 numpy-feedstock#311

[neutrinoceros]

Not sure it's a blocker; My understanding (from conda-forge/conda-forge.github.io#1997) is that numpy 2.0 compat will happen through an automated migration, so it should indeed be okay to just patch pyproject.toml here and ignore numpy 2.0 until further notice.

[mwcraig]

I'll update this first thing tomorrow...

[mwcraig]

@conda-forge-admin please rerender

[mwcraig]

@astrofrog @neutrinoceros -- would you mind giving this a quick look before it gets merged?

[pllim]

FWIW LGTM TYVM

[neutrinoceros]

I think this line is redundant now and pin_compatible("numpy") should be sufficient (even if it wasn't redundant, the constraint is incorrect: it should be >=1.23)

xref https://conda-forge.org/docs/maintainer/knowledge_base/#building-against-numpy

[mwcraig]

Thanks @neutrinoceros and @pllim for reviewing!