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 kristjan.jonsson
Recipients bquinlan, dmalcolm, jnoller, kristjan.jonsson, lukasz.langa, neologix, sandro.tosi, ysj.ray
Date 2011-04-15.19:23:32
SpamBayes Score 0.004153477
Marked as misclassified No
Message-id <>
Now, I'd be super happy to see this strange semantics of PyThread_set_key_value go away.  Its very un-standard and complicates the mapping from an native implementation to the python one.
But I think I did once bring up this issue, and was told that it was a bad idea.
But your logic is sound.  Doing two Sets, is an error regardless.  Hiding the error by ignoring the second set is arbitrarily as bad as ignoring the first thing.
So, if it is possible to fix this and remove this weird special case and cast it into the abyss, then by all means, you have my 10 thumbs up.  Not that it counts for much :)
Date User Action Args
2011-04-15 19:23:33kristjan.jonssonsetrecipients: + kristjan.jonsson, bquinlan, jnoller, dmalcolm, sandro.tosi, ysj.ray, neologix, lukasz.langa
2011-04-15 19:23:33kristjan.jonssonsetmessageid: <>
2011-04-15 19:23:32kristjan.jonssonlinkissue10517 messages
2011-04-15 19:23:32kristjan.jonssoncreate