Changes by Andrew Ziem :
--
nosy: +AndrewZiem
___
Python tracker
<http://bugs.python.org/issue7519>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Andrew Ziem :
--
nosy: +AndrewZiem
___
Python tracker
<http://bugs.python.org/issue2504>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andrew Ziem added the comment:
Well, I no longer need QueryValueEx because I found out
win32file.MoveFileEx() does more easily what I need, but MoveFileEx (see
attachment for working example) shows that the Microsoft Window API
itself creates these "invalid values"
--
Added
Andrew Ziem added the comment:
Yes, regedit does remove the blanks, but this bug report is about
QueryValueEx---not about SetValueEx :). There must be a way to read all
the values compatible with Windows
--
___
Python tracker
<h
Andrew Ziem added the comment:
Attached screenshot shows regedit handles \x00\x00 by showing all the
"invalid values" (each \x00 becomes a line break). More importantly,
Windows apparently reads all the "invalid value" when processing
FileRenameOperations, so my Python pro
Andrew Ziem added the comment:
The bug is noted in the Python source code in file PC/_winreg.c in in
function fixupMultiSZ() where it admits Python does not mimic Microsoft
regedit.exe
--
___
Python tracker
<http://bugs.python.org/issue6
New submission from Andrew Ziem :
QueryValueEx only returns one string when the contents are double null
terminated, yet QueryValueEx works when the string is singly null
terminated.
In Python 2.5.4 on Windows XP Sp3, the first key-value only returns the
first part up to \0\0
