➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.moore
Recipients Pat K, eryksun, paul.moore, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2017-09-28.15:02:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506610953.24.0.466225441844.issue31616@psf.upfronthosting.co.za>
In-reply-to
Content 
Standard Windows behaviour, in my experience, is inherited permissions.

IMO, the current behaviour is correct - we default to an OS-managed secure location for system wide installs, and a user-modifiable location for user installs. If the person doing the install chooses an alternate location, we do not attempt to set policy on that location, but simply inherit the defined permissions.
History
Date User Action Args
2017-09-28 15:02:33paul.mooresetrecipients: + paul.moore, tim.golden, r.david.murray, zach.ware, eryksun, steve.dower, Pat K
2017-09-28 15:02:33paul.mooresetmessageid: <1506610953.24.0.466225441844.issue31616@psf.upfronthosting.co.za>
2017-09-28 15:02:33paul.moorelinkissue31616 messages
2017-09-28 15:02:33paul.moorecreate