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 cboos
Recipients BreamoreBoy, Redoute, cboos, eric.araujo, loewis, steve.dower, tarek
Date 2014-10-26.13:13:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414329192.1.0.978994400088.issue16561@psf.upfronthosting.co.za>
In-reply-to
Content
`--user-access-control auto` doesn't work for me...

With Python 2.7.8 installed ''for all'' in "C:/Program Files (x86)/Python27", an installer built with `bdist_wininst --user-access-control auto` will *not* ask for permission elevation and will crash as described above. If I build the installer with `bdist_wininst --user-access-control force` it will ask for permission elevation and the install will proceed normally. 

Same behavior for the amd64 version of 2.7.8 installed in "C:/Program Files/Python27".

However, one way or the other I think it would be annoying to ask for permission elevation when it's not actually needed, like when python is installed in the default "C:/Python27" location for example. 

So I think a better fix would be to simply *not crash* and fail saying elevated permissions are required. The user can then simply do a "Run as administrator" on the installer from the Windows explorer and things work as expected.
History
Date User Action Args
2014-10-26 13:13:12cboossetrecipients: + cboos, loewis, tarek, eric.araujo, BreamoreBoy, Redoute, steve.dower
2014-10-26 13:13:12cboossetmessageid: <1414329192.1.0.978994400088.issue16561@psf.upfronthosting.co.za>
2014-10-26 13:13:12cbooslinkissue16561 messages
2014-10-26 13:13:11cbooscreate