Author scop
Recipients davin, gvanrossum, rhettinger, scop
Date 2016-08-31.18:22:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472667766.22.0.279097392675.issue27916@psf.upfronthosting.co.za>
In-reply-to
Content
It is not a wholesale search and replace, I have checked each change. There are a lot of places in the tree where monotonic is not appropriate, and those should not be included in the patch. But there is always the possibility that I've missed something, and it's good that there are reviewers.

Granted, some of the changes in this patch might not make a big difference, but they should not hurt either. To me, using monotonic is the right thing to use when dealing with time differences/delays, unless one needs an actual predictable time value anchored at the epoch at the same time for some other purposes. I don't of course insist on that point of view, and would be interested to hear other opinions and if someone can point out flaws/dangers in mine.
History
Date User Action Args
2016-08-31 18:22:46scopsetrecipients: + scop, gvanrossum, rhettinger, davin
2016-08-31 18:22:46scopsetmessageid: <1472667766.22.0.279097392675.issue27916@psf.upfronthosting.co.za>
2016-08-31 18:22:46scoplinkissue27916 messages
2016-08-31 18:22:46scopcreate