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

[Python] Windows wheel cannot be installed on Python 3.8 #23993

Closed
asfimport opened this issue Feb 3, 2020 · 8 comments
Closed

[Python] Windows wheel cannot be installed on Python 3.8 #23993

asfimport opened this issue Feb 3, 2020 · 8 comments

Comments

@asfimport
Copy link
Collaborator

asfimport commented Feb 3, 2020

λ pip install C:\tmp\arrow-verify-release-wheels\pyarrow-0.16.0-cp38-cp38m-win_amd64.whl ERROR: pyarrow-0.16.0-cp38-cp38m-win_amd64.whl is not a supported wheel on this platform.

The wheel came from

https://bintray.com/apache/arrow/download_file?file_path=python-rc%2F0.16.0-rc2%2Fpyarrow-0.16.0-cp38-cp38m-win_amd64.whl

The "m" ABI tag appears to have been removed in Python 3.8

pypa/setuptools#1822

Locally I have pip 20.0.2, wheel 0.34.1, and setuptools 45.1.0.post20200127

Reporter: Wes McKinney / @wesm
Assignee: Krisztian Szucs / @kszucs

Related issues:

Note: This issue was originally created as ARROW-7755. Please see the migration documentation for further details.

@asfimport
Copy link
Collaborator Author

Krisztian Szucs / @kszucs:
@wesm These wheels have not been uploaded to pypi https://pypi.org/project/pyarrow/#files

If I recall correctly the ABI tag issue was fixed during the release process and the cp38m wheels were not removed from bintray.

I suggest to simply delete the cp38m wheels from both bintray channels.

@asfimport
Copy link
Collaborator Author

Wes McKinney / @wesm:
Does the one on PyPI work? Will this happen again in the next release? I lost track of the resolution

@asfimport
Copy link
Collaborator Author

Neal Richardson / @nealrichardson:
IIRC we fixed this by removing the version pin on whatever python build tools package we are using (maybe it was wheel, I don't remember). The "m" issue had been fixed upstream already but we were stuck on an old version. So it should not happen in the next release.

@asfimport
Copy link
Collaborator Author

Krisztian Szucs / @kszucs:
Here is the discussion where we applied the fix after the release 0.16 release and I manually uploaded the new ones: #6353 (comment)

Despite that I managed to manually delete the windows wheels with the previous (wrong) abi tag seems like bintray has kept them.

@asfimport
Copy link
Collaborator Author

Wes McKinney / @wesm:
Alright, but bintray only contains the RC's right? So having a "dirty" RC is not really a big deal as long as it doesn't happen again next time

@asfimport
Copy link
Collaborator Author

Krisztian Szucs / @kszucs:
Bintray have both rc and "official" release artifacts, people use pypi for installing wheels so it should not cause problems.

@asfimport
Copy link
Collaborator Author

Wes McKinney / @wesm:
What is the status of this?

@asfimport
Copy link
Collaborator Author

Krisztian Szucs / @kszucs:
I've removed the dirty pyarrow-0.16.0-cp38-cp38m-win_amd64.* files from the 0.16 bintray release, but I left them under the 0.16.0-rc2 tag.

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

No branches or pull requests

2 participants