Bugs item #1764044, was opened at 2007-07-30 23:30 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1764044&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Python Library Group: Python 2.5 Status: Open Resolution: None Priority: 5 Private: No Submitted By: robs pythonid (robpy1) Assigned to: Nobody/Anonymous (nobody) Summary: copy 2 Initial Comment: I am having problems with the shutil.copy2 I am making a backup program but when I use copy2 the time of my destination file is often two seconds newer than my source file. I was immediately aware that (as in previous bugs) the decimals are always incorrect (so I always use int(os.path.getmtime(source)) but i also see that the seconds are one or two of. It happens in about 10% of the files copied. example of my trace of the check after the copy2 call "shutil.copy2(src,trg)" rereading the mtime gives a difference of one second where the target is 1 second newer. 23:13:50 Non Copied: d:\MyPython\archief.txt , f:\PythonBackup\d-drive\MyPython\archief.txt (1177881701 == 1177881702) N hard to believe? I also used os.utime(trg,(t,t)) to try to correct it but it gives the same error Anybody have the same experience... and how to solve this, just installed python 2.5.1, no help..... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1764044&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
