Message 284278 - Python tracker

➜

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	eric.snow
Recipients	brett.cannon, eric.snow, grahamd, ncoghlan, serhiy.storchaka, steve.dower
Date	2016-12-29.16:51:52
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1483030312.37.0.836957428631.issue29102@psf.upfronthosting.co.za>
In-reply-to

Content
Three reasons come to mind: 1. threads are identified by small integers 2. long, random-looking IDs are not human-friendly, and subinterpreter IDs will be used like thread IDs are 3. related to what Steve said, temporally unique IDs allow us to be confident about whether or not an interpreter has been destroyed (and how many interpreters there have been) Since PyInterpreterState is not a PyObject, using weakrefs to address the third point won't work, right?

Three reasons come to mind:

1. threads are identified by small integers
2. long, random-looking IDs are not human-friendly, and subinterpreter IDs will be used like thread IDs are
3. related to what Steve said, temporally unique IDs allow us to be confident about whether or not an interpreter has been destroyed (and how many interpreters there have been)

Since PyInterpreterState is not a PyObject, using weakrefs to address the third point won't work, right?

History
Date	User	Action	Args
2016-12-29 16:51:52	eric.snow	set	recipients: + eric.snow, brett.cannon, ncoghlan, grahamd, serhiy.storchaka, steve.dower
2016-12-29 16:51:52	eric.snow	set	messageid: <1483030312.37.0.836957428631.issue29102@psf.upfronthosting.co.za>
2016-12-29 16:51:52	eric.snow	link	issue29102 messages
2016-12-29 16:51:52	eric.snow	create