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 r.david.murray
Recipients barry, janzert, petri.lehtinen, r.david.murray
Date 2013-09-16.19:51:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379361095.5.0.274783797523.issue19037@psf.upfronthosting.co.za>
In-reply-to
Content
Hopefully a 2.7 patch would also apply to 3.3, so yes, start there.

For the test, I was thinking that in 3.3+ we could use mock to introduce a delay.  But looking at the code again it isn't obvious that there is a meaningful way to do it that is worth the effort required.  So let's forget about the test for this one...a comment about why the time set is done before the move would be worthwhile, though.
History
Date User Action Args
2013-09-16 19:51:35r.david.murraysetrecipients: + r.david.murray, barry, petri.lehtinen, janzert
2013-09-16 19:51:35r.david.murraysetmessageid: <1379361095.5.0.274783797523.issue19037@psf.upfronthosting.co.za>
2013-09-16 19:51:35r.david.murraylinkissue19037 messages
2013-09-16 19:51:35r.david.murraycreate