[Python-Dev] RELEASED Python 2.4, alpha 2

vincent wehren vincent at visualtrans.de
Fri Aug 6 16:39:11 CEST 2004


Martin v. Löwis wrote:
> vincent wehren wrote:
> 
>> Well, writing a bunch of the registry keys fails. This user has no 
>> rights to
>> write them and is greated with several error messages as in:
>>
>> "Could not write value to key
>> HKEY_CURRENT_USER\Software\Classes\.py Verify that you have
>> sufficient access to that key, or contact your support personnel."
>>
>> .. Same for .pyw, .pyc, *.pyo etc.
>> .. Python.File\shell\open\command
>> .. Python.NoConFile\shell\open\command
>> .. Python.CompiledFile\shell
>> .. Edit with Idle
>>
>> and so on. I was just wondering if the installer should be aware of the
>> rights situation and not try to write those keys in the first place.
> 
> 
> This is very surprising. How unprivileged must a user be so he can't
> write to HKEY_CURRENT_USER? What operating system is this, and how
> was the user created?

This is on Windows XP Professional. This is a plain vanilla "limited 
user" created via the user accounts tool in the control panel.

> 
> MSI does have the notion of unprivileged users, but those are the
> ones that can't write to System32, the All Users profile, and
> HKEY_LOCAL_MACHINE (i.e. non-Administrator, non-Power User users).
> There is no provision (AFAICT) for user that can't write to their
> own registry.

Yes. That makes sense. So I checked the registry with regedit.
"HKEY_CURRENT_USER\Software\Classes" seems - for whatever reason - to be 
busted for this particular user. At least I can't open it manually with 
regedit, so my tentative guess is the same applies to the installer. 
Sorry I didn't check this first!

--
Vincent Wehren




> 
> Regards,
> Martin














More information about the Python-list mailing list