[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2015-03-18 Thread STINNER Victor
STINNER Victor added the comment: I'm no more really interested to add these identifiers. So I just close the issue. -- nosy: +haypo resolution: -> out of date status: open -> closed ___ Python tracker __

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2013-04-25 Thread Kirsten Stevenson
Kirsten Stevenson added the comment: I have added descriptions for CLOCK_BOOTTIME_ALARM and CLOCK_REALTIME_ALARM to the patch. -- nosy: +ransomedheart08 -BreamoreBoy, Jim.Jewett, haypo versions: -Python 3.4 Added file: http://bugs.python.org/file30016/more_clock_ids.patch

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2013-04-18 Thread Mark Lawrence
Mark Lawrence added the comment: If nothing else the patch will need updating to show versionadded as 3.4 instead of 3.3. -- nosy: +BreamoreBoy versions: +Python 3.4 -Python 3.3 ___ Python tracker

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2012-05-06 Thread Ezio Melotti
Changes by Ezio Melotti : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2012-04-13 Thread STINNER Victor
STINNER Victor added the comment: > Any particular reason not to add those? I didn't find yet documentation of: CLOCK_BOOTTIME_ALARM, CLOCK_REALTIME_ALARM For CLOCK_UPTIME_PRECISE, CLOCK_MONOTONIC_PRECISE, CLOCK_REALTIME_PRECISE: I don't know if there are useful. Are they different than the c

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2012-04-13 Thread Jim Jewett
Jim Jewett added the comment: Any particular reason not to add those? -- nosy: +Jim.Jewett ___ Python tracker ___ ___ Python-bugs-lis

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2012-04-12 Thread STINNER Victor
STINNER Victor added the comment: more_clock_ids.patch: add more clock identifiers. Don't add the following clocks: CLOCK_BOOTTIME_ALARM, CLOCK_REALTIME_ALARM, CLOCK_UPTIME_FAST, CLOCK_UPTIME_PRECISE, CLOCK_MONOTONIC_PRECISE, CLOCK_REALTIME_PRECISE. The documentation should be improved :-/ -

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2012-04-11 Thread R. David Murray
Changes by R. David Murray : -- type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2012-04-11 Thread STINNER Victor
STINNER Victor added the comment: Extract of FreeBSD manpage of clock_gettime: The clock_id argument can be one of the following values: CLOCK_REALTIME, CLOCK_REALTIME_PRECISE, CLOCK_REALTIME_FAST for time that increments as a wall clock should; CLOCK_MONOTONIC, CLOCK_MONOTONIC_P

[issue14555] clock_gettime/settime/getres: Add more clock identifiers

2012-04-11 Thread STINNER Victor
New submission from STINNER Victor : Python 3.3 supports the following clock identifiers: * CLOCK_REALTIME * CLOCK_MONOTONIC * CLOCK_MONOTONIC_RAW * CLOCK_HIGHRES * CLOCK_PROCESS_CPUTIME_ID * CLOCK_THREAD_CPUTIME_ID Linux has more clocks: * CLOCK_BOOTTIME * CLOCK_REALTIME_COARSE * CLO