[Python-Dev] this is why we shouldn't call it a "monotonic clock" (was: PEP 418 is too divisive and confusing and should be postponed)

Cameron Simpson cs at zip.com.au
Sat Apr 7 00:11:20 CEST 2012

On 06Apr2012 15:19, I wrote:
| On 06Apr2012 14:31, Steven D'Aprano <steve at pearwood.info> wrote:
| | Here is a non-monotonic sequence:
| | 
| | 1, 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, 8
| | 
| | This isn't steady either, because it jumps backwards.
| | 
| | To be steady, it MUST also be monotonic. If you think that it is appropriate 
| | to call a non-monotonic clock "steady", then I think you should tell us what 
| | you mean by "steady but not monotonic".
| I took steady to mean "never jumps more than x", for "x" being "small",
| and allowing small negatives. If steady implies monotonic and people
| agree that that is so, I'm happy too, and happy that steady is a better
| aspiration than merely monotonic.

I've had some sleep. _Of course_ steady implies monotonic, or it
wouldn't steadily move forwards.
Cameron Simpson <cs at zip.com.au> DoD#743

I went to see a psychiatrist.  He told me I was crazy.  I told him
I wanted a second opinion, so he said, "Ok, you're ugly, too."
        - Rodney Dangerfield

More information about the Python-Dev mailing list