[3.11] Update Python to 3.11.17

[msarahan]

Capture security fixes detailed at https://blog.python.org/2026/10/python-31022-31117/

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-admin]

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:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/37244922126. Examine the logs at this URL for more detail.}

[isuruf]

Can you use https://github.com/conda-forge/python-feedstock/blob/main/recipe/patches/README.md when refreshing the patches? It makes things easier for the next person

[msarahan]

Yes, thanks for the pointer. I will fix the other prs.

[msarahan]

I added an AGENTS.md file in the hopes of saving you the effort of another comment in the future. I will add it to the other PRs if you approve of it.

[h-vetinari]

FWIW, the windows failures in all of these PRs are due to conda-forge/conda-build-feedstock#291