[issue2063] os.times() utime and stime exchanged on windows

Georg Brandl added the comment: Fixed on trunk in r60758. Should this be backported? -- nosy: +georg.brandl resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ _

[issue2063] os.times() utime and stime exchanged on windows

Amaury Forgeot d'Arc added the comment: As a suggestion, we could just run some computation that does no system call: >>> import os >>> os.times() (0.015625, 0.015625, 0.0, 0.0, 0.0) >>> max(xrange(1000)) # this takes half a second on my machine 999 >>> os.times() (0.015625, 0.484375,

[issue2063] os.times() utime and stime exchanged on windows

Facundo Batista added the comment: How can we test it? What can we do to "see" it? -- nosy: +facundobatista __ Tracker <[EMAIL PROTECTED]> __ __

[issue2063] os.times() utime and stime exchanged on windows

Changes by Christian Heimes: -- assignee: -> tiran keywords: +patch nosy: +tiran priority: -> high __ Tracker <[EMAIL PROTECTED]> __ ___ Pytho

[issue2063] os.times() utime and stime exchanged on windows

New submission from Kuang-che Wu: According to document, os.times()[0] is process user time, [1] is system time. However this two value was implemented exchanged on windows. Python all versions have this issue. Attached patch is for trunk. -- components: Extension Modules, Windows files