-
Notifications
You must be signed in to change notification settings - Fork 155
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
pip 20 and pypy - changes needed to pep425tags.py #328
Comments
I see there is an entry in the travis CI for pypy. Is wheel testing with pip20? |
I've switched wheel to use Github Actions instead of Travis, and PyPy3 is part of the matrix now. The test suite does not involve calling pip. I will look at packaging.tags to see if wheel can use them. |
I've implemented the minimum required changes in As for packaging.tags, it cannot replace pep425tags.py, at least not completely. I would also have to decide whether it's okay to add it as a dependency or to vendor it. |
looks good to me. I tried it out and the wheel created is now |
LGTM. I confirm that with the patched version of |
I'm going to cram a couple more PRs in and then make a release. Shouldn't take more than a few days max. |
The resolution of issue pypa#328 removed the custom PyPy tagging from `get_impl_version_info()`, this just cleans up the check that forces PyPy to call that even if `py_version_nodot` was already set.
Hurrah! Thanks @agronholm! ^>^ |
pip20 now uses packaging.tags, not pep425tags.py, but wheel does not seem to have made that change yet. This breaks building wheels for PyPy, since the semantics of the python tag changed.
At a minimum, the pypy-specific stanza should be removed from
get_impl_version_info
, so the implementation becomes a one-linersys.version_info[0], sys.version_info[1]
. Are there plans to transition wheel to packaging.tags?Is there a way to add PyPy to the testing matrix for wheel?See pypa/packaging#233, pypa/packaging#184, and pypa/pip#7629
The text was updated successfully, but these errors were encountered: