py -3 errors in powershell. python does not

[Squalm]

Description: I've had to modify all my run.ps1 files in my algos so that instead of saying py -3 $algoPath they say python $algoPath. This is because powershell runs python as python and not py -3. I installed it using powershell (although I have anaconda set up elsewhere), without modifying anything.

If this is reproducable (or at least, switching to python it continues to work) then it might be worth updating the run.ps1 files.

Expected Result: py -3 starts python as expected.
Actual Result: Error crashes the program.

py : The term 'py' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ py -3
+ ~~
    + CategoryInfo          : ObjectNotFound: (py:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Suggested Solution: switch py -3 to python no other changes necessary.

Steps to reproduce: As described above. Easiest test is attempt to run py -3 in powershell. Then run python.

OS: Windows 10

run.ps1.txt

[Ryan-McPartlan]

Thanks for this detailed report, I will investigate further and potentially make the suggested change

[Ryan-McPartlan]

Are you running run.ps1 directly, or are you running a script like run_match.py?

[Squalm]

I've been using run_match.py. I mentioned using python directly in powershell just because it was an easier demonstration of the issue.