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 kulikjak
Recipients BTaskaya, kulikjak
Date 2020-04-08.18:33:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586370787.89.0.210151618978.issue35455@roundup.psfhosted.org>
In-reply-to
Content
I was speaking for Oracle Solaris 11.4, where CLOCK_THREAD_CPUTIME_ID is now implemented (and we don't need it in older releases). But you are right that other Solaris/SunOS versions might not have this and hence would find this useful.

I can rebase and reopen the original PR, but I cannot test it that well now that our Solaris doesn't use that part of the code (I can change the #define for testing, that should be sufficient).
History
Date User Action Args
2020-04-08 18:33:07kulikjaksetrecipients: + kulikjak, BTaskaya
2020-04-08 18:33:07kulikjaksetmessageid: <1586370787.89.0.210151618978.issue35455@roundup.psfhosted.org>
2020-04-08 18:33:07kulikjaklinkissue35455 messages
2020-04-08 18:33:07kulikjakcreate