Encodes a recent clarification by sheutka regarding the parsing of the replay date. sheutka pointed out that it was represented in file by a Windows nano time stamp (100^-7) measured from January 1st 1601. This allowed us to make clear some procedures that were previously 'magic'.

Author: GraylinKim

sc2reader/readers.py

@@ -3,7 +3,7 @@
 from sc2reader.parsers import *
 from sc2reader.objects import *
 from sc2reader.utils import ByteStream
-from sc2reader.utils import key_in_bases
+from sc2reader.utils import key_in_bases, timestamp_from_windows_time
 
 #####################################################
 # Metaclass used to help enforce the usage contract
@@ -116,8 +116,9 @@ def read(self, filecontents, replay):
         # This might be due to wrong value of the magic constant 116444735995904000
         # or rounding errors. Ceiling or Rounding the result didn't produce consistent
         # results either.
-        replay.date = datetime.fromtimestamp((replay.file_time-116444735995904000)/10000000)
-        replay.utc_date = datetime.utcfromtimestamp((replay.file_time-116444735995904000)/10000000)
+        unix_timestamp = timestamp_from_windows_time(replay.file_time)
+        replay.date = datetime.fromtimestamp(unix_timestamp)
+        replay.utc_date = datetime.utcfromtimestamp(unix_timestamp)
 
         replay.details_data = data
 

sc2reader/utils.py

@@ -196,6 +196,11 @@ def read_header(file):
     #return the release and frames information
     return data[1],data[3]
 
+def timestamp_from_windows_time(windows_time):
+    # This windows timestamp measures the number of 100 nanosecond periods since
+    # January 1st, 1601. First we subtract the number of nanosecond periods from
+    # 1601-1970, then we divide by 10^7 to bring it back to seconds.
+    return (windows_time-116444735995904000)/10**7
 
 import inspect
 def key_in_bases(key,bases):