Rebuild for python 3.13

[regro-cf-autotick-bot]

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

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 code>@<space/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 - please use this URL for debugging.}

[conda-forge-webservices[bot]]

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:

• No valid build backend found for Python recipe for package cytoolz using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[github-actions[bot]]

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.

[dopplershift]

I pulled in a patch for the failing tests from pytoolz/cytoolz#205. As explained in pytoolz/cytoolz#206, the failures are due to newer Python versions (not just 3.13) addressing a limitation in inspect.signature, which changed the test results. Not sure how we feel about bringing in a PR, but the repo does seem a little unresponsive and this will hold up the 3.13 migration for dask.

[dopplershift]

Ok, switched to pytoolz/cytoolz#206 since that fixes some issues unique to Python 3.13. Same caveats about being PR only still apply.

[dopplershift]

Rebased on top of the 1.0 release, which eliminated the need for the patch.

[jakirkham]

Thanks Ryan! 🙏

[jakirkham]

@conda-forge-admin , please re-render

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!