Closed Zeitsperre closed 2 months ago
Took me a minute, but I think I see the problem... I'm betting PyPy's embedded CFFI gets "installed" during their build from CFFI's sdist, not from source. CFFI's setup.py
dynamically adds pycparser
only if it's running under CPython (which it is when we build our sdist)- if the way PyPy's build installs it isn't recalculating the egg-info/dist-info from setup.py, it's going to erroneously list pycparser as a required dep in the bundled metadata.
That dep should really be handled declaratively with an environment marker to exclude PyPy, rather than dynamically injected- if my guess is correct, that will automatically solve the problem everywhere once PyPy updates to a version of CFFI that does it that way.
I've noticed on some builds using PyPy that
pip check
seems to report thatpycparser
is missing. After looking at thesetup.py
, I'm not sure how that could be the case, but all the same, I'm getting build failures: