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
Upon cloning the repo on two different Windows machines (both with the current python version installed via the website) and hitting the setup.bat: Windows pops a cmd echo that it doesn't know the "python" command with the advice to install it from said MS store by not giving any arguments when running the command.
It will only accept the command after installing Python from the MS Store for some reason.
To Reproduce
Steps to reproduce the behavior:
Clone Repo
Have Python already installed
Start Setup.bat
See error above
Expected behavior
Acknowledging the "unofficial" install from the official website and running the setup steps without any issues.
Operating system:
OS: Win10, 64-bit, Home
Version: 22H2
Build 19045.3448
Additional context
Encountered the issue before manually applying the .gitmodules fix
Unsure if it's just some "use our software channel" kind of thing from MS or if Cherno could fix that
The text was updated successfully, but these errors were encountered:
Describe the bug
Upon cloning the repo on two different Windows machines (both with the current python version installed via the website) and hitting the setup.bat: Windows pops a cmd echo that it doesn't know the "python" command with the advice to install it from said MS store by not giving any arguments when running the command.
It will only accept the command after installing Python from the MS Store for some reason.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Acknowledging the "unofficial" install from the official website and running the setup steps without any issues.
Operating system:
Additional context
Encountered the issue before manually applying the .gitmodules fix
Unsure if it's just some "use our software channel" kind of thing from MS or if Cherno could fix that
The text was updated successfully, but these errors were encountered: