Rebuild for python311

[regro-cf-autotick-bot]

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

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/autotick-bot/actions/runs/3330980735, please use this URL for debugging.}

[conda-forge-linter]

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.

[chrisburr]

Looks like this will need patches for Python 3.11: https://bugzilla.redhat.com/show_bug.cgi?id=2025599

[mariusvniekerk]

Looks like this patch needs to be conditional on the python version

[chrisburr]

It looks like this has a bootstrap issue with linux-aarch64 can only be built after a release for linux-64 has been deployed.

[mbargull]

@chrisburr, https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=598222&view=results shows that you cancelled the build on main.
Is that correct? Why did that happen?

[mbargull]

Ah, nvm, https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=597698&view=results happened for the same commit.

[chrisburr]

Yup, the CI triggered twice for some reason so I cancelled one to save resources as we were struggling at the time.

[mbargull]

Yup, the CI triggered twice for some reason so I cancelled one to save resources as we were struggling at the time.

Yeah, figured as much as I saw the other build right after I added the first comment 😅 .
The osx-arm64 build for Py3.11 needs some new workaround, see #143 (comment) .