On Wed, Sep 11, 2019 at 5:36 AM Steve Dower 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
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
On 09Sep2019 1950, Glenn Linderman wrote:
On 9/9/2019 2:48 AM, Steve Dower wrote:
User with administrative privileges are by implication better able to
handle decisions such as this. If they are not, they should not be
administrating a machine.
Most home machines are administered by people
On 9/9/2019 2:48 AM, Steve Dower wrote:
User with administrative privileges are by implication better able to
handle decisions such as this. If they are not, they should not be
administrating a machine.
Most home machines are administered by people that should not be
"administrating" a
Paul answered sufficiently for the venv part, but I wanted to address
this point.
On 09Sep2019 0621, Kyle Stanley wrote:
+1, Particularly on this part. If the user installing Python has administrative
access, I don't see much of a reason for them to have to install a separate
launcher and
On Mon, 9 Sep 2019 at 06:28, Kyle Stanley wrote:
> Steve Dower wrote:
> > It also means that regular users can install packages without needing to be
> > admin, and without corrupting other user's installs.
>
> Does this have any advantage over using a virtual environment? I can imagine
> this
Terry Jan Reedy wrote:
> "This installer also installs the multiversion py.exe launcher if doing
so would not be a downgrade. If you have admin access, we recommend
installing one py.exe for all users. See xxx for how to use py.exe.
[ ] Install py.exe for all users.
+1, Particularly on this
On 8/29/2019 11:35 AM, Steve Dower wrote:
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
On 8/29/2019 4:52 AM, Armen Michaeli wrote:
Hi all,
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
On 29Aug2019 0851, Serhiy Storchaka wrote:
29.08.19 18:35, Steve Dower пише:
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
29.08.19 18:35, Steve Dower пише:
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
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
12 matches
Mail list logo
