-
Notifications
You must be signed in to change notification settings - Fork 12
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
Support PEP 639 #70
Comments
Hi @iudeen thank you very much for reporting this. The status of PEP 639 is still Draft, so the new format is still not a standard. |
Hey! Thanks, yes I just went through the discord discussions. Seems like it's delayed because of a Moon launch 😅 |
This is provisionally accepted, so it's time to implement, I think. It would be great if we could also do validation on the license specifiers. Maybe even have a strict mode that validates that they are already normalized (maybe combined with #179?) |
As per latest PEP0639 deprecates subkeys in license - https://peps.python.org/pep-0639/#deprecate-license-key-table-subkeys
This causes the following error in projects that adopted the new standard. (Especially the ones that adopted Hatch)
As per PEP document:
The text was updated successfully, but these errors were encountered: