You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pywhlobf currently (as of 0.2.3) generates an uninstallable wheel on linux due to an error in the platform tag in the output filename:
As an example:
Running pywhlobf test-0.1.0-py3-none-any.whl dist will produce the output dist/test-0.1.0-cp38-cp38-linux-x86_64.whl. Attempting to run pip3.8 install dist/test-0.1.0-cp38-cp38-linux-x86_64.whl will produce the error ERROR: test-0.1.0-cp38-cp38-linux-x86_64.whl is not a supported wheel on this platform. because linux-x86_64 is not a valid platform tag, it should be linux_x86_64 (note the use of an underscore rather than a dash). Manually renaming the file to the correct pattern solves the issue.
This seems to be related to changes in wheel.bdist_wheel.get_platform in versions 0.35.0 and above.
The text was updated successfully, but these errors were encountered:
hutchisr
changed the title
Tool generates incorrect platform tag in output filename when run on Linux
Tool generates incorrect platform tag in output filename when run on Linux when using wheel version >0.34.2
Apr 14, 2022
pywhlobf currently (as of 0.2.3) generates an uninstallable wheel on linux due to an error in the platform tag in the output filename:
As an example:
Running
pywhlobf test-0.1.0-py3-none-any.whl dist
will produce the outputdist/test-0.1.0-cp38-cp38-linux-x86_64.whl
. Attempting to runpip3.8 install dist/test-0.1.0-cp38-cp38-linux-x86_64.whl
will produce the errorERROR: test-0.1.0-cp38-cp38-linux-x86_64.whl is not a supported wheel on this platform.
becauselinux-x86_64
is not a valid platform tag, it should belinux_x86_64
(note the use of an underscore rather than a dash). Manually renaming the file to the correct pattern solves the issue.This seems to be related to changes in
wheel.bdist_wheel.get_platform
in versions 0.35.0 and above.Related: #1
The text was updated successfully, but these errors were encountered: