If I check the last modification time of a file in Python, move
You are currently reading a thread in /g/ - Technology
If I check the last modification time of a file in Python, move the file to another hard drive with the same file system and check the time again, it returns a different value.
Same os
Same computer
Same file
What is going on?
>>55491862
what OS
what file system
post code
>>55491862
>move the file to another hard drive
You're writing the file in another hard drive, not just moving to the same one.
Of course it will return another value.
>>55491890
Win 7
NTFSos.path.getmtime()
>>55491921
I want to compare the modification timestamp, not the creation timestamp.
>>55491946
Different file system
Different os
>>55491946
round it. filesystems can have issues with microseconds
>>55492187
The difference is over a whole second though. But why would the modification time be affected at all? I'm not modifying the file.
>>55491983
>he thinks creation is not a modification
>>55492445
It's not. It's a modification of the file itself, at least it should be.
By the way, I fixed the issue according to >>55492187 's advice. I just added an error margin of 5 seconds to my calculations.
I'm a genius.