Skip to content
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

unsupported platform tag 'linux_x86_64' #684

Open
0382 opened this issue Aug 1, 2023 · 3 comments
Open

unsupported platform tag 'linux_x86_64' #684

0382 opened this issue Aug 1, 2023 · 3 comments

Comments

@0382
Copy link

0382 commented Aug 1, 2023

I got a error while upload

Binary wheel 'WignerSymbol-0.0.6-cp38-cp38-linux_x86_64.whl' has an unsupported platform tag 'linux_x86_64'

Related github action: https://github.com/0382/WignerSymbol-pybind11/actions/runs/5727291479/job/15519392532

It is built with python -m build -w command. If this is not supported, them why python -m build will generate such tag?

@sigmavirus24 sigmavirus24 transferred this issue from pypa/twine Aug 1, 2023
@sigmavirus24
Copy link
Member

I've moved this to the packaging-problems repository because this isn't a bug in twine. Twine sent the package to pypi.org where it was rejected.

@merwok
Copy link

merwok commented Aug 1, 2023

«linux» is not really a defined platform, it could be hundreds of configurations. The platform tag only exists for you to build on a controlled environment and deploy to your servers using the same environment (possibly with a private index in the middle, which could explain why twine did not block the upload).

For public PyPI, see the manylinux specification and the cibuildwheel tool.

@link2xt
Copy link

link2xt commented Oct 16, 2023

My package contains a binary that is portable to basically any Linux because it is statically linked to musl libc. Same can be said about Go binaries. I then start this binary as a subprocess and use stdio to communicate with it from the Python code. Yet PyPI forces me to use "manylinux"/"musllinux" tags, and in the end the package cannot be installed in Termux because Android has bionic libc and has only "linux_x86_64" tag when I run this:

>>> from pip._internal.utils.compatibility_tags import get_supported
>>> get_supported()

Yet if I install the binary manually, it works perfectly in Termux.

See also https://pypi.org/project/ziglang/, it is actually a static zig binary inside, yet it has manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64 tags instead of a perfectly correct in this case linux_aarch64 tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants