-
Notifications
You must be signed in to change notification settings - Fork 969
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
Bug: uv publish
missing METADATA
file
#8030
Comments
What build backend are you using, and could you share more details about your project and your setup? Additionally, |
Since I just got the same issue, here's a project: https://github.com/Avasam/typed-D3DShot/tree/24954b8122448926b9afddc1c245796b5e9165a0
Backend: setuptools |
Thanks stackoverflow https://stackoverflow.com/a/76757413 I renamed the dist-info folder and it worked. I kept the |
I just took a closer look, and in my case it's seemingly a confusion with The package name is
We see the issue is a mixup with
|
The spec requires normalizing the name and the version in distribution filenames (https://packaging.python.org/en/latest/specifications/binary-distribution-format/#escaping-and-unicode). Missing normalization caused #8030, this PR adds a warning for it.
Since setuptools violates the wheel filenames spec (pypa/setuptools#3777), we have to use the raw filename when publishing to get through https://github.com/pypi/warehouse/blob/50a58f3081e693a3772c0283050a275e350004bf/warehouse/forklift/legacy.py#L1133-L1155. Tested with ``` cargo run publish aviary.gsm8k-0.7.6-py3-none-any.whl --publish-url https://test.pypi.org/legacy/ ``` Fixes #8030
The problem here is that the wheel filename is invalid: All We're doing two things about this, one is adding a warning for invalid filenames (#8203), the other is adding a workaround specifically for setuptools (#8204), so this wheel can be uploaded, as it can with twine. |
The spec requires normalizing the name and the version in distribution filenames (https://packaging.python.org/en/latest/specifications/binary-distribution-format/#escaping-and-unicode). Missing normalization caused #8030, this PR adds a warning for it.
Oh thank you @konstin, nice! Just seeking one point of clarification on your above comment, for my understanding:
Did you mean to say |
yes, sorry |
I am using
uv==0.4.20
and just migrated a publish GitHub Action in a repo using this workspace layout for several packages touv publish
.Before, publish worked correctly, but with
uv publish
I am getting:Any idea what's going on here? I think this is a
uv publish
bug given my change was an atomic change, and I was previously usinguv build
successfullyThe text was updated successfully, but these errors were encountered: