-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
maturin upload
: Invalid distribution file. PKG-INFO not found
#2362
Comments
Not sure what's going on, can you try |
Same error
|
Related pypi code will investigate later when I'm free. |
Unsure if related, but I am unable to get
I'm using my PyPI username and API token. |
That is expected, the error message is pretty clear, see https://pypi.org/help/#apitoken you must use |
Thanks for finding the relevant code. Now I see that the issue is caused by the package data (
causing the common prefix to be
Another solution could be to set the
|
Could setting the |
|
Bug Description
Maturin upload command is failing to upload the source distribution because PyPi complains about
PKG-INFO
not found. The action job logging messages can be seen here: https://github.com/ZJaume/heliport/actions/runs/12141036958/job/33852428765#step:4:39It seems that is checking for
heliport/PKG-INFO
but the tarball hasheliport-0.8.0/PKG-INFO
. It is strange, because for the previous version it worked and the version suffix was there also. Did PyPi changed the packaging criteria? Maybe I am missing something?Your maturin version (
maturin --version
)1.7.7
Your Python version (
python -V
)Python 3.10.12
Your pip version (
pip -V
)pip 24.0
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
I think nobody can reproduce this with my package, as I am the only person with permissions, but I did the upload manually from my machine and still fails.
maturin upload heliport-0.8.0.tar.gz
and obtainThe text was updated successfully, but these errors were encountered: