Skip to content
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

Implement PEP-600: Future 'manylinux' Platform Tags for Portable Linux Built Distributions #9077

Closed
mayeut opened this issue Oct 31, 2020 · 6 comments · Fixed by #9170
Closed
Labels
C: wheel The wheel format and 'pip wheel' command PEP implementation Involves some PEP
Milestone

Comments

@mayeut
Copy link
Member

mayeut commented Oct 31, 2020

What's the problem this feature will solve?
Allows to install packages that use a PEP600 platform tag

Describe the solution you'd like
Update packaging to 20.5 (pypa/packaging#345)

Alternative Solutions

Additional context
Given the purpose of PEP600, this should be the last - well in the foreseeable future at least - update regarding support of manylinux platform tags in pip

@uranusjr
Copy link
Member

Is the packaging update the only thing we need to do? We can add this to 20.3 (due mid-November) if that’s the case.

@mayeut
Copy link
Member Author

mayeut commented Oct 31, 2020

@uranusjr,

yes, updating packaging is the only thing required on pip end (but packaging 20.5 is not released yet, @di and @pradyunsg should have visibility on when it will be released).

I've been doing some tests around the manylinux ecosystem and updating packaging to its master branch solves this issue:

@uranusjr
Copy link
Member

Cool, I’ll add this to the 20.3 milestone as a reminder.

@uranusjr uranusjr added this to the 20.3 milestone Oct 31, 2020
@uranusjr uranusjr added C: wheel The wheel format and 'pip wheel' command PEP implementation Involves some PEP labels Oct 31, 2020
mayeut added a commit to mayeut/auditwheel that referenced this issue Nov 7, 2020
mayeut added a commit to mayeut/auditwheel that referenced this issue Nov 7, 2020
mayeut added a commit to mayeut/auditwheel that referenced this issue Nov 7, 2020
mayeut added a commit to mayeut/auditwheel that referenced this issue Nov 7, 2020
mayeut added a commit to mayeut/auditwheel that referenced this issue Nov 7, 2020
@pradyunsg pradyunsg removed this from the 20.3 milestone Nov 11, 2020
mayeut added a commit to mayeut/auditwheel that referenced this issue Nov 14, 2020
@h-vetinari
Copy link

Would be good to have this in, I believe? Considering the relative rarity of pip-releases, having PEP600-compatibility should IMHO be a priority.

@mayeut
Copy link
Member Author

mayeut commented Nov 28, 2020

Given the comment in pypa/packaging#345 (comment), I guess this will end up in 20.3 even though the 20.3 milestone has been removed from this issue.

@pradyunsg pradyunsg added this to the 20.3 milestone Nov 28, 2020
@pradyunsg
Copy link
Member

pradyunsg commented Nov 28, 2020

Well, I thought we'd cut pip 20.3 before packaging 20.5 got ready, but Brett was faster than I was. ;)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C: wheel The wheel format and 'pip wheel' command PEP implementation Involves some PEP
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants