> On Aug 27, 2019, at 10:44 AM, Mariatta wrote:
>
> (cross posting to python-committers, python-dev, core-workflow)
>
> PEP 581: Using GitHub Issues has been accepted by the steering council, but
> PEP 588: GitHub Issues Migration plan is still in progress.
>
> I'd like to hear from core deve
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 insta
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 u
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 w
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 (recomme
