updated v3.8.15

[mbargull]

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-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.

[mbargull]

@conda-forge-admin, please rerender

[github-actions]

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

I tried to rerender for you, but it looks like I wasn't able to push to the 3.8.15 branch of mbargull-feedstocks/python-feedstock. Did you check the "Allow edits from maintainers" box?

NOTE: PRs from organization accounts cannot be rerendered because of GitHub permissions.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/python-feedstock/actions/runs/3515097137.

[mbargull]

@conda-forge-admin, please rerender

[github-actions]

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/python-feedstock/actions/runs/3515129492.

[mbargull]

@conda-forge-admin, please restart ci

[jakirkham]

Thanks Marcel! 🙏

[h-vetinari]

Hey @mbargull @jakirkham

The merge of this PR to the 3.8 branch failed to build for one PPC version (unfortunately, the more relevant OpenSSL 3 one), and I'm now seeing resolver errors due this. Would you be so kind to restart it please?

[jakirkham]

Tried restarting CI. Though we may need a re-render of this branch

Note: Had to create a totally new build to get the updated token (since that was changed between when this PR was merged and now)

[h-vetinari]

I think this is now running into the setuptools 66 stuff in the downstreams: tests...

TEST START: /home/conda/feedstock_root/build_artifacts/pkg_cache/setuptools-66.1.1-pyhd8ed1ab_0.conda

Traceback (most recent call last):
[...]
RuntimeError: Could not read JSON repodata file (/home/conda/feedstock_root/build_artifacts/pkg_cache/cache/51e90255.json) parse error line 90: subdir mismatch

[jakirkham]

Could you please send a PR to either constrain this to setuptools <66.0.0a or if necessary skip this test altogether?

[h-vetinari]

Could you please send a PR to either constrain this to setuptools <66.0.0a or if necessary skip this test altogether?

I don't think downstreams: can work with a constraint? Perhaps best to skip it for now?

[isuruf]

I think this is now running into the setuptools 66 stuff in the downstreams: tests...

No. This should have been fixed by conda-forge/conda-forge-repodata-patches-feedstock#388. Please revert your changes.

[h-vetinari]

This should have been fixed by conda-forge/conda-forge-repodata-patches-feedstock#388.

But it wasn't fixed by that. John restarted the travis build which failed ~5h ago, the PR you linked was merged >24h ago.

Please revert your changes.

There's not much to revert (especially considering how aarch64 was skipped due to long-obsolete constraints on drone), but in any case: #619

[mbargull]

Downstream test issues are non-functional due to conda/conda-build#4750 (i.e., an issue we experience through conda-mambabuild caused by a conda-build+libsolv=0.7.23 incompatibility).

[isuruf]

Sorry, wrong PR. Correct PR is conda-forge/boa-feedstock#61