Author nanonyme
Recipients nanonyme
Date 2018-01-17.18:09:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516212552.32.0.467229070634.issue32587@psf.upfronthosting.co.za>
In-reply-to
Content
MSDN documents that REG_MULTI_SZ is not supposed to have \0\0 anywhere else than in the end. The comment in  
https://github.com/python/cpython/blob/a5293b4ff2c1b5446947b4986f98ecf5d52432d4/PC/winreg.c#L504
clearly shows that Python has the assumption that this specification is actually correct. However, Microsoft is violating it eg in https://technet.microsoft.com/en-us/library/cc960241.aspx which prevents you from reading that registry key in Python at all. This is a list which is treated as pairs:
"""
foo

meep
bar
"""
so you can have empty items which in Windows semantics means "remove this file". This results in a string like "foo\0\0meep\0\bar\0\0". I'm proposing relaxing Python registry handling semantics because it's clearly Microsoft isn't following this either
History
Date User Action Args
2018-01-17 18:09:12nanonymesetrecipients: + nanonyme
2018-01-17 18:09:12nanonymesetmessageid: <1516212552.32.0.467229070634.issue32587@psf.upfronthosting.co.za>
2018-01-17 18:09:12nanonymelinkissue32587 messages
2018-01-17 18:09:12nanonymecreate