-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Clarify that the latest Python might not work #2767
Conversation
I wasted a lot of time not realizing Python 3.11 isn't supported because of the lack of clarity in the line I've edited.
Actually, I get the same error no matter what version of Python 3 I use. Why is that? Isn't this issue supposed to be fixed already? |
As stated above, the problem was not related to the Python 3 version. This change is not needed because we work with and test pre-release versions of Python to ensure that our installation process is compatible with them on the day that they are released.
Please look thru your error log for the string |
@cclauss I looked through the 8 I used Python2.7 to get around this, but I don't understand why the issue is occurring.
Can you clarify what you mean by "your error log"? What would this be on a Windows machine? I don't see an |
Python 2 died 1,065 days ago on 1/1/2020 os it should no longer be used. |
Well, I just realize that The failing module was Thanks very much for your help @cclauss! In case you still had some interest in the output upon failure, here it is. The command we ran was just
|
Line 8:
|
Yeah I realized, I mentioned - but I'm sure you're very busy and I know I'm a bit wordy. I appreciate all your help. Thanks again! |
I wasted a lot of time not realizing Python 3.11 isn't supported because of the lack of clarity in the line I've edited.
Checklist
Description of change
Remove unclear reference to "current" Python version, that does not necessarily mean "current."
Someone please let me know if I need to re-title my PR. I don't see the relevant prefix, but maybe "docs:" ?