Python for Windows (python-3.7.4.exe) location confusing
Is it possible for the installer to check whether or not there is a pre-existing system-wide launcher, and only do the complicated stuff if it is actually there? -jJ
On 10Sep2019 2120, Jim J. Jewett wrote:
Is it possible for the installer to check whether or not there is a pre-existing system-wide launcher, and only do the complicated stuff if it is actually there?
I'm not sure what you're referring to here. If there's a pre-existing launcher of the same or higher version, it won't try to install it and won't ask for administrative privileges. This has worked since Python 3.5. But you mention "only do ... stuff if ... there" - what stuff are you referring to? The installer should do *less* if it's partially installed already, not more. Cheers, Steve
On Wed, Sep 11, 2019 at 5:36 AM Steve Dower <steve.dower@python.org> wrote:
But you mention "only do ... stuff if ... there" - what stuff are you referring to? The installer should do *less* if it's partially installed already, not more.
My understanding was that (1) You believe the py.exe launcher should be installed per-user, at least if python itself is installed per-user. (2) In the past (~3.4) it was installed for all users (even if python was per-user). (3) If there is an old py.exe in the system-wide location, that will mask any per-user py.exe. (4) Therefore, py.exe defaults to installing in the system-wide location, to avoid being masked. (5) You were wondering whether 3.4 is old enough to stop worrying. My suggestion is to instead check whether or not there is actually a py.exe in the system-wide location. If so, then go ahead and update or remove it. If not, then you don't need to worry about whether or not 3.4 is sufficiently old -- it is irrelevant on this particular system. -jJ
participants (2)
-
Jim J. Jewett -
Steve Dower