[Python-Dev] 3.5 release schedule PEP (original) (raw)
Paul Moore p.f.moore at gmail.com
Sat Sep 27 11:55:44 CEST 2014
- Previous message: [Python-Dev] 3.5 release schedule PEP
- Next message: [Python-Dev] 3.5 release schedule PEP
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 27 September 2014 06:08, Terry Reedy <tjreedy at udel.edu> wrote:
Pip on Windows should act like a normal Windows program. If I install Python for all users, I expect pipped packages to be installed for all users too, unless I specify otherwise. If installation (for all users) requires admin privileges, I expect a UAC box to pop up and ask for the admin password. This is pretty routine, at least with Win7. Most every program I install does this either on installation or on first running. Some Windows operations also pop up a box. There are only a few things that require that I actually login as an admin user.
The main problem is that there is little or no prior art on Windows for console programs that require elevation. Those few that do need it require you to start the program from an elevated prompt, but that's not a good user experience.
But having said that, I agree with your point, the UAC changes are designed specifically to get people used to the "think about what you're doing" approach, and we should be doing the same. Paul
- Previous message: [Python-Dev] 3.5 release schedule PEP
- Next message: [Python-Dev] 3.5 release schedule PEP
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]