Force siphash for 3.9

[matthiasdiener]

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.

[matthiasdiener]

@conda-forge-admin, please rerender

[matthiasdiener]

This is ready for review.

[matthiasdiener]

A gentle ping for a review @conda-forge/python

[matthiasdiener]

Another gentle ping @conda-forge/python

[xhochy]

@conda-forge-admin please rerender

[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/12755212698. Examine the logs at this URL for more detail.}

[xhochy]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

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

[matthiasdiener]

Another gentle ping for a review @conda-forge/python

[jakirkham]

@conda-forge-admin , please re-rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

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

[jakirkham]

@conda-forge-admin , please relint

[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/14389904095. Examine the logs at this URL for more detail.}

[jakirkham]

Seeing errors like this on Windows CI:

D:\bld\python-split_1742335590860\work\Modules\_ctypes\cfield.c(1508,1): error C2099: initializer is not a constant [D:\bld\python-split_1742335590860\work\PCbuild\_ctypes.vcxproj]

Doesn't look like the changes in this PR would affect it. Maybe we can try merging in the latests upstream changes to see if that helps?

[jakirkham]

Closing and reopening so CI picks up the latest changes in the upstream branch

[schribl]

@matthiasdiener @jakirkham I had similar compile issues on Windows for #776 so I did a test without any change in #778 and it still failed. So I assume this issue is similar.

Small update:
I did update #778 as I discoverd that libffi was updated. And with the downgrade of libffi 3.4.6 -> 3.4.2 the windows build works again. I would expect similar results for 3.9

[matthiasdiener]

The compile issue seems to have been resolved.

[jakirkham]

Thanks Matthias and Thomas! 🙏

Glad to hear we got this working

Had one minor comment below. After that think we can merge

[matthiasdiener]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

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

[jakirkham]

Thank you for adding all these fixes (especially to such an old version of Python). Having consistency across them is very helpful for users! 🙏

Queued to automerge

[conda-forge-admin]

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

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed
• rerender called: passed

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

[jakirkham]

Ah when resolving conflicts we missed a build/number. Sorry about that 🤦‍♂️

In any event there was a Python 3.9 patch release just merged: #786

So this should get picked up with that rebuild