-
Notifications
You must be signed in to change notification settings - Fork 12.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
x.py expects python3.exe on Windows #75156
Comments
Yes, x.py does not work if you install python then use |
Very odd; I use "python x.py" on Windows just fine.
|
Is this the Windows version of #75034? |
@RalfJung it's entirely different. This issue is some kind of user environment issue. There is no
Also tried official Python installed in Windows virtual machine and there is no |
Oh I see. But if |
🤷♂️ I'm not involved with the upstream Python 😄 |
IMO it would be good if someone who actually uses Python on Windows could bring this to their attention in their bugtracker. :) |
FWIW I've been running As far as I can tell @Kixiron or @RDambrosio016 could you provide instructions for reproducing whatever issue you are having? |
There is now a tool called |
I'm going to close this since no one's been able to reproduce the issue. Feel free to reopen if you can replicate this. |
Seems to be the root cause of #72523, @RDambrosio016 also encountered a similar (but less dramatic) issue. On windows it seems that x.py expects an executable of python3 to be named exactly python3.exe and will encounter varying errors while spawning internal python processes when these conditions are not met
The text was updated successfully, but these errors were encountered: