Rebuild for python310

[regro-cf-autotick-bot]

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

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.

This package has the following downstream children:

And potentially more.

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. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, 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/1473492242, 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.

[xhochy]

@conda-forge-admin please rerender

[bollwyvl]

Upstream is pretty quiet... it might be this doesn't work generally, anymore...

Though it might just need an ansible pin, as suggested over on #3 (comment)

[bollwyvl]

Another alternative: we could go to noarch, as it would just not be solveable on windows because ansible.

[bollwyvl]

Had a look at this: most of the issues seen during build have been solved upstream... we could just make up a version, and ship with the current head off github, i guess... might do better to ask for an upstream release rather than carrying lots of patches, though...

[bollwyvl]

Created ansible/ansible-jupyter-kernel#93

[xhochy]

Another alternative: we could go to noarch, as it would just not be solveable on windows because ansible.

Yes, that would be a good path forward. Still, doesn't solve all the errors :)

[bollwyvl]

closing in fabor of #6