Rebuild for python312

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update python312.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

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.

_{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/6269971942, 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.

[h-vetinari]

meson.build:15:15: ERROR: <PythonExternalProgram '$PREFIX/bin/python' -> ['$PREFIX/bin/python']> is not a valid python or it is missing distutils

A full log can be found at $SRC_DIR/builddir/meson-logs/meson-log.txt

[pkgw]

Paralleling the discussion in conda-forge/gobject-introspection-feedstock#69, I believe that the workaround here is to add setuptools as a build dep, until mesonbuild/meson#7702 is fixed.

The non-cross Python 3.9 / PyPy builds have started failing here — I feel like I've been seeing such failures elsewhere ... I guess something has gotten borked in that configuration?

[xhochy]

The non-cross Python 3.9 / PyPy builds have started failing here — I feel like I've been seeing such failures elsewhere ... I guess something has gotten borked in that configuration?

I have seen the same error in other feedstocks as well. It gets fixed by pinning pypy to 7.3.11, the issues got introduced in 7.3.12.

[pkgw]

@xhochy Would you recommend that we apply that pin, or would it be better to figure out how to fix the new version?

[xhochy]

I think both would be best but I failed to pin pypy in builds.

[h-vetinari]

I have seen the same error in other feedstocks as well. It gets fixed by pinning pypy to 7.3.11, the issues got introduced in 7.3.12.

I don't think that's a reasonable solution, because it will bifurcate off from all other artefacts that only get rebuilt for newest pypy. I'd suggest to raise an issue on the pypy feedstock and simply ignore the failures here for now - they don't matter in the context of the 3.12 migration.

[pkgw]

Aha, looks like we have an issue to link to: conda-forge/pypy3.6-feedstock#109

[regro-cf-autotick-bot]

Due to the bot-rerun label I'm closing this PR. I will make another one as appropriate. This was generated by https://github.com/regro/cf-scripts/actions/runs/6339838041