Message304153
| Author | vstinner |
|---|---|
| Recipients | brett.cannon, christian.heimes, gvanrossum, lukasz.langa, methane, rhettinger, serhiy.storchaka, terry.reedy, vstinner |
| Date | 2017-10-11.15:40:56 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1507736456.39.0.213398074469.issue31415@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Why global _PyTime_GetWinPerfCounterWithInfo() is needed at all? It seems to me that _PyTime_GetPerfCounterWithInfo() can be used instead. Smaller API is better. I chose to expose _PyTime_GetWinPerfCounterWithInfo() to make my change as small as possible. I didn't want to break the old time.clock() clock by mistake. By the way, time.clock() is deprecated since Python 3.3. It's maybe time to drop it? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-10-11 15:40:56 | vstinner | set | recipients: + vstinner, gvanrossum, brett.cannon, rhettinger, terry.reedy, christian.heimes, methane, lukasz.langa, serhiy.storchaka |
| 2017-10-11 15:40:56 | vstinner | set | messageid: <1507736456.39.0.213398074469.issue31415@psf.upfronthosting.co.za> |
| 2017-10-11 15:40:56 | vstinner | link | issue31415 messages |
| 2017-10-11 15:40:56 | vstinner | create | |