|
From: | Roy Badami |
Subject: | Re: [Duplicity-talk] changed files not being backed up |
Date: | Fri, 23 Dec 2011 17:27:51 +0000 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0 |
On 23/12/2011 17:22, Roy Badami wrote:
Hmm, on further investigation, regardless of what Windows calls it, python returns the creation time as the ctime on Windows:On 23/12/2011 16:54, Wolfgang Rohdewald wrote:Am Freitag, 23. Dezember 2011, 08:55:23 schrieb Kenneth Loafman:Change time, ctime, is for any modification of the file, i.e. content ormetadata.true for Linux, not true for Windows. On Windows, ctime is the true creation time and stays the same when the content changes.http://en.wikipedia.org/wiki/MAC_times#Change_time_and_creation_time_.28ctime.29Does Windows *really* call it's creation time "ctime"?
st_ctime - platform dependent; time of most recent metadata change on Unix, or the time of creation on Windows)
Seems like broken behaviour in os.stat to me, but I guess if it's documented it's not a bug.
-- Roy Badami Roboreus Ltd Third Floor The Place 175 High Holborn London WC1V 7AA
[Prev in Thread] | Current Thread | [Next in Thread] |