Python in the Windows 10 May update

Re:Python in the Windows 10 May update by noname120 on Friday June 07, 2019 @09:55AM (#20124486)

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-...

[ Parent | on HN ]

Re:Python in the Windows 10 May update by sametmax on Friday June 07, 2019 @10:36AM (#20124931)

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

[ Parent | on HN ]

Re:Python in the Windows 10 May update by pizza on Friday June 07, 2019 @12:54PM (#20126526)

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

[ Parent | on HN ]

Re:Python in the Windows 10 May update by ChrisSD on Friday June 07, 2019 @10:18AM (#20124719)

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

[ Parent | on HN ]

Re:Python in the Windows 10 May update by vbezhenar on Friday June 07, 2019 @10:47AM (#20125065)

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

[ Parent | on HN ]

Re:Python in the Windows 10 May update by noname120 on Friday June 07, 2019 @10:28AM (#20124842)

They could have used another mechanism than PATH.

[ Parent | on HN ]

Re:Python in the Windows 10 May update by vetinari on Friday June 07, 2019 @11:14AM (#20125364)

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.

[ Parent | on HN ]

Re:Python in the Windows 10 May update by mwcampbell on Friday June 07, 2019 @10:23AM (#20124785)

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.

[ Parent | on HN ]