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 steve.dower
Recipients SilentGhost, anshul6, eryksun, paul.moore, r.david.murray, random832, steve.dower, stutzbach, tim.golden, zach.ware
Date 2015-12-03.06:00:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1449122456.0.0.359770214838.issue25778@psf.upfronthosting.co.za>
In-reply-to
Content
All registry values are blobs and it's up to the caller to decide how to read it - the "types" are hints and are not binding.

I don't mind the default behavior being to trim at the first null, but it is a lossy operation on our side and so we really ought to provide an easy way to get the true value back. Otherwise, we couldn't easily write scripts in Python to detect registry values with embedded nulls :)
History
Date User Action Args
2015-12-03 06:00:56steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, stutzbach, r.david.murray, SilentGhost, zach.ware, eryksun, random832, anshul6
2015-12-03 06:00:55steve.dowersetmessageid: <1449122456.0.0.359770214838.issue25778@psf.upfronthosting.co.za>
2015-12-03 06:00:55steve.dowerlinkissue25778 messages
2015-12-03 06:00:55steve.dowercreate