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 639 #16620

Closed
befeleme opened this issue Sep 3, 2024 · 4 comments · Fixed by #16949
Closed

Implement PEP 639 #16620

befeleme opened this issue Sep 3, 2024 · 4 comments · Fixed by #16949

Comments

@befeleme
Copy link

befeleme commented Sep 3, 2024

What's the problem this feature will solve?
Standardized licensing metadata will in time unify the currently largely chaotic landscape.

Describe the solution you'd like
See: https://peps.python.org/pep-0639
PEP 639 has been provisionally accepted with one of the conditions being implementation in PyPI.

@befeleme befeleme added feature request requires triaging maintainers need to do initial inspection of issue labels Sep 3, 2024
@ewdurbin
Copy link
Member

ewdurbin commented Sep 3, 2024

PyPI uses https://github.com/pypa/packaging to parse and validate metadata, so it will need an update to support the new metadata version, keys, and deprecations.

I've opened draft PRs for that and the packaging docs at:

Once those PRs (or something that supersedes them) are merged, implementation in PyPI can begin.

@ewdurbin
Copy link
Member

Draft PR is now up at #16949 awaiting merge/release of pypa/packaging#828.

@ewdurbin
Copy link
Member

ewdurbin commented Nov 8, 2024

#16949 is now ready for review with the release of packaging 24.2

@ewdurbin
Copy link
Member

PEP 639 implementation is live and online for PyPI now. We'll keep an eye out for issues filed if folks run into any issues as adoption takes off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants