[issue23946] Invalid timestamps reported by os.stat() when Windows FILETIME structures are mistakenly reset.

Eryk Sun added the comment: > The code of posixmodule.c looks very different now. The conversion code was moved to FILE_TIME_to_time_t_nsec() in Python/fileutils.c. time_t is a signed 64-bit integer type, so there's no immediate problem storing 1601-01-01 as the negative (pre-epoch) Unix t

[issue23946] Invalid timestamps reported by os.stat() when Windows FILETIME structures are mistakenly reset.

Irit Katriel added the comment: The code of posixmodule.c looks very different now. It this issue still relevant? -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___

[issue23946] Invalid timestamps reported by os.stat() when Windows FILETIME structures are mistakenly reset.

New submission from Cristi Fati: In WinPE environment (at least this is where I found it, but there might be cases where this issue could be spotted in normal Windows), some folders might have some of the FILETIME structures reset (because of RAMDrive?). When the conversion between WIN style (