On: Python in the Windows 10 May update

[noname120]

It looks like this update breaks already-installed Python execution if its position in the PATH environment variable is after the WindowsApps folder. [1]

[1] https://devblogs.microsoft.com/python/python-in-the-windows-...

[sametmax → noname120]

That's why any good tutorial on Python for Windows recommend using the "py -x.y" command, and not the "python" command.

[pizza → sametmax]

TIL about the py command, and I've been using Python on Windows for many years now. Thanks!

[ChrisSD → noname120]

That is how PATH works. An installer would have to be doing something seriously wonky to get that wrong.

[vbezhenar → ChrisSD]

IMO installer should check existing PATH and warn user that this installation will change his python executable.

[noname120 → ChrisSD]

They could have used another mechanism than PATH.

[vetinari → noname120]

bash does exactly that - it has command_not_found_handle function and distributions define it, so they can offer package installation for any command not found.

[mwcampbell → noname120]

Yep, I ran into this some months ago with an insider build. IIRC though, I had manually added Python to my PATH. So I just adjusted the order and kept using my existing Python install.