Message241987
> We don't have the same definition of the unit "seconds" :-)
Or, please forget my comment, I watched the first 4 items of os.times(). I didn't notice the difference of the 5th item, os.times()[4].
The bad news is that only the first two items of os.times() are filled on Windows :-( I don't think that Python 2.7 provides a monotonic clock on Windows.
static PyObject *
os_times_impl(PyModuleDef *module)
{
#ifdef MS_WINDOWS
FILETIME create, exit, kernel, user;
HANDLE hProc;
hProc = GetCurrentProcess();
GetProcessTimes(hProc, &create, &exit, &kernel, &user);
/* The fields of a FILETIME structure are the hi and lo part
of a 64-bit value expressed in 100 nanosecond units.
1e7 is one second in such units; 1e-7 the inverse.
429.4967296 is 2**32 / 1e7 or 2**32 * 1e-7.
*/
return build_times_result(
(double)(user.dwHighDateTime*429.4967296 +
user.dwLowDateTime*1e-7),
(double)(kernel.dwHighDateTime*429.4967296 +
kernel.dwLowDateTime*1e-7),
(double)0,
(double)0,
(double)0);
... |
|
Date |
User |
Action |
Args |
2015-04-24 22:37:21 | vstinner | set | recipients:
+ vstinner, gregory.p.smith, benjamin.peterson, r.david.murray, mcjeff, koobs |
2015-04-24 22:37:21 | vstinner | set | messageid: <1429915041.21.0.427402181449.issue23863@psf.upfronthosting.co.za> |
2015-04-24 22:37:21 | vstinner | link | issue23863 messages |
2015-04-24 22:37:20 | vstinner | create | |
|