Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2012-March/118020.html below:

[Python-Dev] Rename time.steady(strict=True) to time.monotonic()?

• 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 ]

> This seems like it should have been a PEP, or maybe should become a PEP.

I replaced time.wallclock() by time.steady(strict=False) and
time.monotonic() by time.steady(strict=True). This change solved the
naming issue of time.wallclock(), but it was a bad idea to merge
monotonic() feature into time.steady(). It looks like everybody
agrees, am I wrong?

Victor

• 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 ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4