[Python-Dev] Drop the new time.wallclock() function? (original) (raw)
Matt Joiner anacrolix at gmail.com
Sat Mar 24 00:06:46 CET 2012
- Previous message: [Python-Dev] Drop the new time.wallclock() function?
- Next message: [Python-Dev] sharing sockets among processes on windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yes, call it what it is. monotonic or monotonic_time, because that's why I'm using it. No flags.
I've followed this thread throughout, and I'm still not sure if "steady" gives the real guarantees it claims. It's trying to be too much. Existing bugs complain about backward jumps and demand a clock that doesn't do this. The function should guarantee monotonicity only, and not get overcomplicated. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120324/1862b16c/attachment.html>
- Previous message: [Python-Dev] Drop the new time.wallclock() function?
- Next message: [Python-Dev] sharing sockets among processes on windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]