4 ms·
The point is that python3 was already in place, and the package on the official website only created the python executable, so the stub linked to the Microsoft
by 1_player 6y ago
The point is that python3 was already in place, and the package on the official website only created the python executable, so the stub linked to the Microsoft Store wasn't overwritten.
This is no different than macOS. If you don't overwrite the existing stubs, you get the "install xcode" message when running git or cc.
But if Apple does it, it's OK because they're the good guys.
- vetinari 6y agoThere's no overwriting stubs in MacOS. With SIP enabled, not even root can write into /usr (the apple stub is /usr/bin/git). Many users use git from homebrew; once you do 'brew install git', the stub won't bother you, despite homebrew not overwriting anything. It is just earlier in the $PATH. And that's the issue with Windows: the standard installer does create python3.exe, it is just later in the %PATH%, because Microsoft placed the stub in one of the early directories. Normal, well behaved installer, which places its entry at the end won't be able to override anything.
- 1_player 6y agoThat's what I meant by overwriting: just placing it earlier in your $PATH. Overriding perhaps was a better word.