-
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
Use regular PEP 425 interpreter tags for PyPy wheels #329
Comments
How does this relate to issue gh-328 and the pypytags branch? I think @agronholm was going to merge that and release |
Turns out this is a duplicate of #328, but there's still a remnant of the old custom PyPy tagging in the code (it just doesn't do anything meaningful any more). I noticed the duplication when I went to add a NEWS entry. |
ncoghlan
added a commit
to ncoghlan/wheel
that referenced
this issue
Jan 27, 2020
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.
agronholm
pushed a commit
that referenced
this issue
Jan 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We'd like to go back to using standard PEP 425 tags for PyPy wheels (see pypa/packaging#233 and pypa/pip#7629), but that entails having PyPy build wheels with the regular leading interpreter tag, rather than the current PyPy specific one.
I'm working on a PR to temporarily add back support for the custom tags to
pip
, but would also like to contain the problem on thewheel
side, and will post a PR for that shortly.The text was updated successfully, but these errors were encountered: