-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
python 3.9 pip install fails (tar.gz instead of .whl) #6228
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
Comments
There are no python 3.9 wheels yet. We'll build them for upcoming releases, but we typically don't go back to build wheels for earlier releases. Right now, we have to wait a bit for our CI/build infrastructure to support python 3.9 and for our dependencies (numpy is the main one) to publish 3.9 wheels. We plan to have releases for v2 and v3 relatively soon (v2.3.3 and v3.0.0 alpha releases), so there will be updated wheels in time. |
Perfect. No problems :) Waiting eagerly and wish luck. Thank you for good job |
I have the same error types using W10 and Py3.9 > since package 'wheel' is not installed. |
As both 2.3.4 and 2.3.5 now have wheels for Python 3.9, I think we can close this issue. If there are still issues with installation, feel free to open a new ticket! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Uh oh!
There was an error while loading. Please reload this page.
How to reproduce the behaviour
Python 3.9 command
Python 3.9 output:
requirements.txt
Dockerfile (to reproduce from 0)
docker image test
docker image test output
Python 3.8 command
Python 3.8 output
(The very exact moment i change Dockerfile to 3.8 or lower it starts to download wheel and all works)
I suppose that spaCy wheel is not yet ready for python 3.9?
Your Environment
I use docker (linux) AND windows 10. Fails same for both. Clean install of python 3.9 (no packages in freeze)
Possibly related issues
pandas-dev/pandas#32045
The text was updated successfully, but these errors were encountered: