[Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
Antoine Pitrou
solipsis at pitrou.net
Sat Mar 24 09:39:28 CET 2012
More information about the Python-Dev mailing list
Sat Mar 24 09:39:28 CET 2012
- Previous message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Next message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 23 Mar 2012 22:38:19 -0500 Brian Curtin <brian at python.org> wrote: > On Fri, Mar 23, 2012 at 18:38, Yury Selivanov <yselivanov.ml at gmail.com> wrote: > > On 2012-03-23, at 7:28 PM, Brian Curtin wrote: > >> This seems like it should have been a PEP, or maybe should become a PEP. > > > > Why? AFAIK Victor just proposes to add two new functions: monotonic() and > > steady(). > > We just previously had "Drop time.monotonic() function, rename > time.wallclock() to time.steady()" checked in a few weeks ago, and now > we're renaming a variation on time.steady to time.monotonic? What's > the next move? > > I'm not paying close attention here but there's a lot of movement > going on. Figuring out the API before we get too deep is probably a > good idea. Agreed with Brian. Obviously the API needs further discussion, judging by Victor's own multiple changes of mind on the subject. Regards Antoine.
- Previous message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Next message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list