-
-
Notifications
You must be signed in to change notification settings - Fork 284
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
Wheel file generated with maturin 1.7.6 doesn't check with twine 5.1.1 #2335
Comments
Yeah I don't think we'll fix it on |
messense
added
wontfix
This will not be worked on
and removed
bug
Something isn't working
labels
Nov 29, 2024
2 tasks
termoshtt
added a commit
to Jij-Inc/ommx
that referenced
this issue
Dec 4, 2024
- Use twine 5.1.1 for validating wheels until pypa/gh-action-pypi-publish#309 is merged. - twine 5.1.1 does not supports metadata 2.4, thus fix `maturin == 1.7.5` since it uses metadata 2.4 until 1.7.6 PyO3/maturin#2335
nikpau
added a commit
to nikpau/pytsa
that referenced
this issue
Dec 4, 2024
pypa/twine#1180 was merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
With maturin 1.7.6, the wheel file generated by
pip wheel
won't be validated withtwine check
with twine >= 5.1.1.The root cause seems that maturin 1.7.6 switched to metadata version to
2.4
, which is not yet supported by twine 5.1.1 - so this might have to be addressed on twine side and it seems that there is the PR for this.So,the reason I opened this issue is not to request fix this issue on maturin side- rather, I intend this issue to be a note for anyone else who encountered this situation. If this is inappropriate, please feel free to close this.
Your maturin version (
maturin --version
)1.7.6
Your Python version (
python -V
)3.9.20
Your pip version (
pip -V
)pip 23.0.1
What bindings you're using
pyo3
Does
cargo build
work?If on windows, have you checked that you aren't accidentally using unix path (those with the forward slash
/
)?Steps to Reproduce
pip wheel
[email protected] check
, then it complains as follows:The text was updated successfully, but these errors were encountered: