
On 29Aug2019 0152, Armen Michaeli wrote:
The installer dialog mentions Python will be installed in something like $USERPROFILE\AppData\Local\Programs\Python\Python37-32 while at the same time suggesting it will be made available for all users through the "Install launcher for all users (recommended)". This is confusing -- if the package is to be made available for everybody, it shouldn't be installed somewhere under the profile folder of whomever is installing it, normally other people can't even access this folder at all.
It should be installed in %Program Files(x86)%, unless it is a private installation indeed (the "Install launcher for all users" is unchecked).
Is this an omission of sorts? Is one expected to correct this themselves, during installation -- I don't see where one would even specify the installation folder?
The launcher is installed separately from the main Python installation. So everyone will have access to the launcher, but only you will have access to the Python install - if someone else on the machine installs Python as well, they won't have to install the launcher. It also means that regular users can install packages without needing to be admin, and without corrupting other user's installs.
The settings you are looking for are under the second big button that says "Customize installation // Choose location".
This is the second query like this I've had (well, forever, really) in the last couple of months, and my inclination is to make the launcher a per-user install by default. The main reason for making it as a per-machine install by default was because there was no other way to replace the Python 3.4 launcher, but I suspect that's less of an issue now. (If the old one wasn't replaced, it would take precedence over the new per-user one and wouldn't be able to find some newer versions of Python.)
If that checkbox were not present on the front page of the installer and everything was only installed for you, would you still have raised this question? I'm trying to see if that would be a satisfactory fix.
Cheers, Steve