Serhiy Storchaka <storchaka+cpyt...@gmail.com> added the comment: > Currently, Python exposes "thread identifiers" as unsigned long values across > multiple modules:
It happened not so long ago. In 3.6 and earlier "thread identifiers" are signed integers. See issue6532, it was massive change. This issue was deferred for long time due to the afraid of breaking the word. And it still was not tested with third-party code. >> What happens for code that uses e.g. "%x" to format thread ids? >It's okay for the opaque object to have a int() conversion. What happens for C code that uses "%lu" to format thread ids? ---------- nosy: +serhiy.storchaka _______________________________________ 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
