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 slw07g
Recipients slw07g
Date 2014-08-10.06:01:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1407650482.35.0.308980176266.issue22178@psf.upfronthosting.co.za>
In-reply-to
Content
The explanation of the 3rd index of the tuple returned from _winreg.QueryInfoKey(key) explains that it is a long representing 100s of nanoseconds since 1/1/1600.

However, when I use this value and convert to the actual date using 
startDate = datetime(1600,1,1)
lastModified = QueryInfoKey(key)[2]
print "%s" % startDate + timedelta(seconds=lastModified*(10**-9)*100) 

The date is about right except for the year value, it's off by one.

I suspect the documentation should say the value in the tuple is the time since 1/1/1601 instead of 1/1/1600. This would corroborate Microsoft's documentation that makes references to 1/1/1601 (i.e. http://technet.microsoft.com/en-ca/aa393040(v=vs.90).aspx)
History
Date User Action Args
2014-08-10 06:01:22slw07gsetrecipients: + slw07g
2014-08-10 06:01:22slw07gsetmessageid: <1407650482.35.0.308980176266.issue22178@psf.upfronthosting.co.za>
2014-08-10 06:01:22slw07glinkissue22178 messages
2014-08-10 06:01:21slw07gcreate