➜

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 serhiy.storchaka
Recipients benjamin.peterson, ncoghlan, pdox, pitrou, r.david.murray, serhiy.storchaka, tim.peters
Date 2017-10-01.21:13:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506892425.52.0.213398074469.issue31622@psf.upfronthosting.co.za>
In-reply-to
Content 
> 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?
History
Date User Action Args
2017-10-01 21:13:45serhiy.storchakasetrecipients: + serhiy.storchaka, tim.peters, ncoghlan, pitrou, benjamin.peterson, r.david.murray, pdox
2017-10-01 21:13:45serhiy.storchakasetmessageid: <1506892425.52.0.213398074469.issue31622@psf.upfronthosting.co.za>
2017-10-01 21:13:45serhiy.storchakalinkissue31622 messages
2017-10-01 21:13:45serhiy.storchakacreate