V7.3.12

[mattip]

Checklist

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

Update the recipe. I removed version from the jinja2 template since python3.8 does not have a 7.3.12 release. Looking at the changelog for 7.3.12, I don't see anything that is critical for 3.8, but the backported fixes for functools may allow some progress with the pandas feedstock. Anyhow I think CPython and PyPy python3.8 will be dropped soon after the migration of CPython 3.12 starts, which should not too far in the future.

I would like to add a solution for #101 as well.

[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) and found it was in an excellent condition.

[mattip]

CI is green. Anyone want to review?

[mattip]

I commented out the fix for #101. That issue will have to wait for another day.

[mattip]

@conda-forge-admin, please rerender

[mattip]

Since the controversial fix for #101 was removed, I will merge this.

[h-vetinari]

Quick question: are you planning to do the aarch/ppc builds like for the last version bump (#99)?

[mattip]

I want to make some progress with pandas first, perhaps there are more problems in the feedstock that need to be fixed.