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 eryksun
Recipients eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-08-02.21:03:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1564779818.5.0.792639086919.issue37746@roundup.psfhosted.org>
In-reply-to
Content
The STANDARD_RIGHTS_* and SPECIFIC_RIGHTS_ALL constants aren't used much in practice. Do you have a particular case that needs them?

I don't think we have direct use for the standard rights constants in winreg. For example, deleting a key via winreg.DeleteKeyEx internally opens a handle with the required DELETE access. Also, kernel key objects don't even support SYNCHRONIZE access (i.e. they can't be waited on).

There's also the generic rights that object types map to sets of standard and specific rights: GENERIC_READ (0x8000_0000), GENERIC_WRITE (0x4000_0000), GENERIC_EXECUTE (0x2000_0000), and GENERIC_ALL (0x1000_0000). But, here again, winreg doesn't really need this. It already includes the pre-mapped generic key rights: KEY_READ, KEY_WRITE, KEY_EXECUTE, and KEY_ALL_ACCESS (except GENERIC_EXECUTE actually maps to KEY_EXECUTE | KEY_CREATE_LINK).
History
Date User Action Args
2019-08-02 21:03:38eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower
2019-08-02 21:03:38eryksunsetmessageid: <1564779818.5.0.792639086919.issue37746@roundup.psfhosted.org>
2019-08-02 21:03:38eryksunlinkissue37746 messages
2019-08-02 21:03:38eryksuncreate