Message127306
| Author | maubp |
|---|---|
| Recipients | loewis, maubp, shaurz |
| Date | 2011-01-28.14:50:21 |
| SpamBayes Score | 3.3604445e-07 |
| Marked as misclassified | No |
| Message-id | <1296226221.96.0.846664004322.issue10148@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm also seeing this on 32bit Windows XP using Python 3.1.2, and Python 3.2rc1 on a local NTFS filesystem. e.g. from os.stat(filename).st_mtime after using shutil.copy2(...) 1293634856.1402586 source 1293634856.1402581 copied I've been using shutil.copy2 then expecting st_mtime will be equal (or at least that the copy file will be newer than the original). As you can see in this case, the copy is sometimes a fraction older. The same issue occurs using shutil.copy then shutils.copystat (probably not a surprise). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-01-28 14:50:22 | maubp | set | recipients: + maubp, loewis, shaurz |
| 2011-01-28 14:50:21 | maubp | set | messageid: <1296226221.96.0.846664004322.issue10148@psf.upfronthosting.co.za> |
| 2011-01-28 14:50:21 | maubp | link | issue10148 messages |
| 2011-01-28 14:50:21 | maubp | create | |