Author Pat K
Recipients Pat K, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-09-28.11:49:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <cbd8532a-dd68-a5d0-5a20-2b3279944579@gmail.com>
In-reply-to <1506596987.6.0.466225441844.issue31616@psf.upfronthosting.co.za>
Content
Thank you for the explanation. I understand this is intentional. However
user without such knowledge of inheritable permissions might want to
default the installation directory to the old one (C:\PythonXX) and
could easily run into this issue without knowing. IMHO extra security
check or explicit warning wouldn't hurt here. Just my 5c.

On 9/28/2017 1:09 PM, Eryk Sun wrote:
> 
> Eryk Sun <eryksun@gmail.com> added the comment:
> 
> The "(I)" flag in an icacls entry means it's inherited from the parent directory. The installer doesn't override these inherited permissions. Currently, it's your responsibility to do this if you install to a custom directory such as C:\Python36. 
> 
> Starting with Python 3.5, a per-machine installation defaults to a subdirectory of Program Files. This system directory only grants standard users generic read and execute access for subdirectories and files. A per-user installation defaults to the user's Programs directory (i.e. %LocalAppData%\Programs). This directory grants full control to the user, administrators, and the system. Other users have no access.
> 
> ----------
> components: +Windows
> nosy: +eryksun, paul.moore, steve.dower, tim.golden, zach.ware
> type:  -> enhancement
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue31616>
> _______________________________________
>
History
Date User Action Args
2017-09-28 11:49:24Pat Ksetrecipients: + Pat K, paul.moore, tim.golden, zach.ware, eryksun, steve.dower
2017-09-28 11:49:24Pat Klinkissue31616 messages
2017-09-28 11:49:23Pat Kcreate