-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] setuptools._vendor.pyparsing.ParseException on pypy wiht tox with setuptools 60.9.0 #3107
Comments
I'm guessing that the relevant change (history) is the bump of packaging. |
This repro is quite difficult to follow given that it requires pypy, rust, openssl, and still the error happens in an isolated pip environment without any access to the source. |
Would it be helpful if I put together a Dockerfile that built an environment for reproducing this? There's unfortunately not much I can do about the moving pieces here, they're what's involved in reproducing this. (As for the isolated pip environment, I can take even less responsibility for that!) |
I've made some progress, but thanks. Still working on it... |
I'm now confident 2d6cc80 is implicated. |
The issue stems from the fact that importlib_metadata returns different types for
An empty string is returned on PyPy. I would have expected an iterable or None. |
Hmmm, on pypy cffi is pre-installed and ships with the interpreter AFAIK (it's for this reason that we don't even list it as a dependency on pypy! https://github.com/pyca/cryptography/blob/main/pyproject.toml#L8). Where does the metadata come from in that case? I guess in the first instance the question is whether PyPy is in the wrong for this to be an empty string, or whether it's an edge case that |
My guess is the use-case is under-specified. What I can say is that the data is coming from the egg-info path:
|
setuptools version
60.9.0
Python version
pypy 3.7
OS
ubuntu linux
Additional environment information
No response
Description
Runnign tox with pypy and setuptools 60.9.0 produces:
The full traceback can be seen in this CI run: https://github.com/pyca/cryptography/runs/5192122892?check_suite_focus=true
Pinning to a previous version of setuptools resolves this, as can be seen at pyca/cryptography#6868
Expected behavior
The dependencies are installed correctly, as happens on previous versions of setuptools.
How to Reproduce
tox -e pypy3-nocoverage
Output
The text was updated successfully, but these errors were encountered: