Antoine Pitrou <pit...@free.fr> added the comment: 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) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31622> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
