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 neologix
Recipients Arfrever, neologix, pitrou, tim.peters, vstinner
Date 2013-11-28.16:51:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0uOP2EwLJqjprwweN1+5f=+sUwfPWgz05Kkuyx6hxcSg@mail.gmail.com>
In-reply-to <1385649353.15.0.541823293601.issue19787@psf.upfronthosting.co.za>
Content
> Antoine Pitrou added the comment:
>
> Calling it _PyThread_set_key_value is prone to confusion.
> Ideally we would fix PyThread_set_key_value's behaviour. Are there users of the function outside from CPython?

The question is why does it behave this way in the first place?
Maybe for sub-interpreters?
History
Date User Action Args
2013-11-28 16:51:16neologixsetrecipients: + neologix, tim.peters, pitrou, vstinner, Arfrever
2013-11-28 16:51:16neologixlinkissue19787 messages
2013-11-28 16:51:16neologixcreate