homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Arfrever, BreamoreBoy, Claudiu.Popa, emaste, harrison.grundy, jcea, koobs, larry, pitrou, r.david.murray, trent, vstinner
Date 2015年06月11日.22:55:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1434063347.82.0.10299307769.issue15745@psf.upfronthosting.co.za>
In-reply-to
Content
test_utime_ns.patch: rewrite _test_utime_ns(). It now uses constant timestamps for atime and mtime with a resolution of 1 us.
The test will fail if the internal function of os.utime() has a resolution of 1 sec (utime() with time_t) of if the resolution of filesystem timestamp is worse than 1 us.
In practice on buildbots, it looks like the effective resolution of 1 us (FreeBSD, Solaris), 100 ns (Windows) or 1 ns (Linux). So 1 us should work on all buildbot slaves.
test_utime_ns.patch doesn't call os.utime() on directories, only on a regular file. I don't understand the purpose of testing with a directory. Are we testing the OS or Python?
History
Date User Action Args
2015年06月11日 22:55:47vstinnersetrecipients: + vstinner, jcea, pitrou, larry, trent, Arfrever, r.david.murray, Claudiu.Popa, BreamoreBoy, koobs, emaste, harrison.grundy
2015年06月11日 22:55:47vstinnersetmessageid: <1434063347.82.0.10299307769.issue15745@psf.upfronthosting.co.za>
2015年06月11日 22:55:47vstinnerlinkissue15745 messages
2015年06月11日 22:55:47vstinnercreate

AltStyle によって変換されたページ (->オリジナル) /