Message120154
| Author |
belopolsky |
| Recipients |
belopolsky, eric.araujo, kristjan.jonsson, michael.foord, pitrou |
| Date |
2010年11月01日.18:55:35 |
| SpamBayes Score |
2.209467e-09 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTimHSkhcxDsZT4ncrJT=abPW34RZ2YkLwPLQ2Jne@mail.gmail.com> |
| In-reply-to |
<1288634987.11453.9.camel@localhost.localdomain> |
| Content |
On Mon, Nov 1, 2010 at 2:09 PM, Antoine Pitrou <report@bugs.python.org> wrote:
..
> The problem is time.clock(), since it does two wildly different things
> depending on the OS.
> I would suggest to deprecate time.clock() at the same time as we add
> time.wallclock(). For the Unix-specific definition of time.clock(),
> there is already os.times() (which gives even richer information).
+1, but doing something like that should be discussed on python-ideas
first. We should also weigh this against other proposals such as
exposing gettimeofday. |
|