-
Notifications
You must be signed in to change notification settings - Fork 966
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 Metadata Version 2.2 #9660
Comments
There's a couple levels of 'validation' that could happen for the
Are we OK with only doing 1 & 2? (cc @pfmoore) |
From my perspective just allowing 2.2 when no |
I think (1) is reasonable. The PEP allows wheels to set |
Got it. I was taking this from the original issue and thought I was missing something in the PEP. I'll update the OP accordingly. If all we need to do is 1) then this is straightforward. |
What's the next step for this? Is it just waiting on a PR? |
Yes. |
scikit-build-core set the metadata version to 2.2 that is not yet supported by PyPI. This was due to a dynamic pyproject.toml section being used. pypi/warehouse#9660
scikit-build-core set the metadata version to 2.2 that is not yet supported by PyPI. This was due to a dynamic pyproject.toml section being used. pypi/warehouse#9660
What's the problem this feature will solve?
Since PEP 643 is accepted, PyPI should start accepting Metadata 2.2 distributions. See PyO3/maturin#564.
Describe the solution you'd like
Allow
Metadata-Version: 2.2
to pass the legacy upload endpoint’s form validation, and validate the correspondingDynamic
field.The latter part could be a bit tricky since
Dynamic
is not allowed for wheels. Not sure how it could be best handled (I don’t have much experience with WTForm).Additional context
https://www.python.org/dev/peps/pep-0643/
The text was updated successfully, but these errors were encountered: