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 Jim.Jewett, Mark.Shannon, amaury.forgeotdarc, benjamin.peterson, jcea, ncoghlan, pitrou, ron_adam, scoder
Date 2012-04-11.12:11:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334145929.3328.13.camel@localhost.localdomain>
In-reply-to <>
> According to PEP 384 (Defining a Stable ABI) the thread state object
> is opaque, so we should be free to add or remove fields.

Mmh, be aware the stable ABI is only a restricted part of the official
API. There are APIs which are not part of the stable ABI, but are still
public and officially supported.

That said, I agree the thread state *structure* shouldn't be part of the
official API. If necessary, we can provide accessors for some of its
Date User Action Args
2012-04-11 12:11:02pitrousetrecipients: + pitrou, jcea, amaury.forgeotdarc, ncoghlan, scoder, ron_adam, benjamin.peterson, Mark.Shannon, Jim.Jewett
2012-04-11 12:11:02pitroulinkissue13897 messages
2012-04-11 12:11:02pitroucreate