Message120192
| Author | kristjan.jonsson |
|---|---|
| Recipients | belopolsky, eric.araujo, kristjan.jonsson, michael.foord, pitrou |
| Date | 2010-11-02.00:05:32 |
| SpamBayes Score | 8.419699e-05 |
| Marked as misclassified | No |
| Message-id | <1288656333.86.0.348093042163.issue10278@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Certainly. I was going to put this simple code in time.py when I realized that time was a C module. The main point, as Antoine points out, is that time.clock() means two seriously different things on the two main platforms, and time.clock() is potentially inadequate on one of them. I put in the patch since it was quick to do, but I'll provoke a discussion on python-ideas for now. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-11-02 00:05:33 | kristjan.jonsson | set | recipients: + kristjan.jonsson, belopolsky, pitrou, eric.araujo, michael.foord |
| 2010-11-02 00:05:33 | kristjan.jonsson | set | messageid: <1288656333.86.0.348093042163.issue10278@psf.upfronthosting.co.za> |
| 2010-11-02 00:05:32 | kristjan.jonsson | link | issue10278 messages |
| 2010-11-02 00:05:32 | kristjan.jonsson | create | |