Eryk Sun <eryk...@gmail.com> added the comment:
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). ---------- nosy: +eryksun _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37746> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
