Implement PEP-600: Future 'manylinux' Platform Tags for Portable Linux Built Distributions
See original GitHub issueWhat’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
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
PEP 600 – Future 'manylinux' Platform Tags for Portable Linux ...
This will allow package maintainers to take advantage of new tags more quickly, while making better use of limited volunteer time. Non-goals ...
Read more >cmeel
... Specifying Minimum Build System Requirements for Python Projects; PEP 600, Future 'manylinux' Platform Tags for Portable Linux Built Distributions ...
Read more >What's the deal with Python wheels?
In Python we say that wheels are distribution packages. ... 'PEP 600 – Future “manylinux” Platform Tags for Portable Linux Built ...
Read more >Python users: important changes in pip 20.3 (dependency resolver ...
Support for PEP 600: Future ' manylinux ' Platform Tags for Portable Linux Built Distributions. Documentation improvements: Resolver migration guide, ...
Read more >Changelog - pip documentation v22.3.1
Add support for PEP 600: Future 'manylinux' Platform Tags for Portable Linux Built Distributions. (#9077). The new resolver now resolves packages in a ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Cool, I’ll add this to the 20.3 milestone as a reminder.
Well, I thought we’d cut pip 20.3 before packaging 20.5 got ready, but Brett was faster than I was. 😉