➜

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 benjamin.peterson, ncoghlan, pdox, pitrou, r.david.murray, tim.peters
Date 2017-10-01.19:15:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <9e711472-2fe0-ce7f-2a85-fc3e1bbf9d5e@free.fr>
In-reply-to <1506884827.3579751.1124253528.4077A83D@webmail.messagingengine.com>
Content 
Le 01/10/2017 à 21:07, Benjamin Peterson a écrit :
> 
> signal.pthread_kill and pdox's proposed time.pthread_getcpuclockid on
> https://github.com/python/cpython/pull/3756

Given how specialized (and of little actual use) those functions are, I
don't think it's much of a problem if they misbehave if you deliberately
pass an invalid thread id.

At least it sounds less of a problem than breaking all code that expects
a thread id to be an integer.

(btw, pthread_getcpuclockid returns ESRCH on Linux if called with an
invalid thread id)
History
Date User Action Args
2017-10-01 19:15:08pitrousetrecipients: + pitrou, tim.peters, ncoghlan, benjamin.peterson, r.david.murray, pdox
2017-10-01 19:15:08pitroulinkissue31622 messages
2017-10-01 19:15:08pitroucreate