PyPy 7.3.12

[h-vetinari]

no more 3.8

Following conda-forge/pypy3.6-feedstock#105

[conda-forge-webservices]

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]

Any idea why mamba cannot solve the constraints?

Mamba failed to solve:
 - python 3.9.17.* 0_73_pypy
 - pypy3.9 7.3.12.*
 - python_abi 3.9.* *_pypy39_pp73

with channels:

The reported errors are:
- Encountered problems while solving:
-   - package pypy3.9-7.3.12-h9557127_2 has constraint python 3.9.* *_7.3_pypy \
-     conflicting with python-3.9.17-0_73_pypy
- 

[mattip]

@isuruf fixed the typo in the feedstock in conda-forge/pypy3.6-feedstock#106.

[h-vetinari]

Do we want to merge this with broken CI, or explicitly exclude 7.3.12 for aarch/ppc? (given that those arches have lower priority than other things right now, as discussed post-merge in conda-forge/pypy3.6-feedstock#105)

CC @mattip @isuruf

[mattip]

If I understand correctly, merging this as-is will implicitly exclude 7.3.12 for aarch64/pppc64le. So the difference is whether we explicitly exclude or implictly exclude? If that is the case, I don't think it really matters one way or the other.

[mattip]

I am in favor of whatever will lead to this being merged more quickly. I would like to move forward with testing pandas, but need 7.3.12 to proceed.

[mattip]

Thanks!