Message 306265 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	belopolsky, pitrou, vstinner
Date	2017-11-15.12:13:43
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<c42d2aff-eaf0-a84b-904b-868d45be30ba@free.fr>
In-reply-to	<1510710529.8.0.213398074469.issue32025@psf.upfronthosting.co.za>

Content
Le 15/11/2017 à 02:48, STINNER Victor a écrit : > > Would it be possible to not provide the function if it's not supported by a platform? Probably, yes. > Do you know platforms which don't support time.thread_time()? Any POSIX platform which doesn't have CLOCK_THREAD_CPUTIME_ID? It's an optional feature in the POSIX spec. > Do you want to add time.thread_time_ns() with nanosecond resolution (PEP 564) ? Yes, I think so. > It seems like macOS doesn't implement CLOCK_THREAD_CPUTIME_ID but provides thread_info() which can be used by suming user and system times. I don't have a macOS machine to test on, though :-)

Le 15/11/2017 à 02:48, STINNER Victor a écrit :
> 
> Would it be possible to not provide the function if it's not supported by a platform?

Probably, yes.

> Do you know platforms which don't support time.thread_time()?

Any POSIX platform which doesn't have CLOCK_THREAD_CPUTIME_ID?  It's an
optional feature in the POSIX spec.

> Do you want to add time.thread_time_ns() with nanosecond resolution (PEP 564) ?

Yes, I think so.

> It seems like macOS doesn't implement CLOCK_THREAD_CPUTIME_ID but
provides thread_info() which can be used by suming user and system times.

I don't have a macOS machine to test on, though :-)

History
Date	User	Action	Args
2017-11-15 12:13:43	pitrou	set	recipients: + pitrou, belopolsky, vstinner
2017-11-15 12:13:43	pitrou	link	issue32025 messages
2017-11-15 12:13:43	pitrou	create