6 ms·
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] h
by noname120 7y ago
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-10-may-2019-update/#comments-35 https://devblogs.microsoft.com/python/python-in-the-windows-...
- ChrisSD 7y agoThat is how PATH works. An installer would have to be doing something seriously wonky to get that wrong.
- noname120 7y agoThey could have used another mechanism than PATH.
- vetinari 7y agobash 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.
- vbezhenar 7y agoIMO installer should check existing PATH and warn user that this installation will change his python executable.
- mwcampbell 7y agoYep, 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.
- sametmax 7y agoThat's why any good tutorial on Python for Windows recommend using the "py -x.y" command, and not the "python" command.
- pizza 7y agoTIL about the py command, and I've been using Python on Windows for many years now. Thanks!
- deleted 7y ago[deleted]