Message204703
Attached patch fix PyThread_set_key_value() instead of adding a new function.
I prefer fix_set_key_value.patch instead of pythread_set_key_value.patch because I feel bad of keeping a buggy function and having to decide between a correct and a buggy version of the same function.
> Deja vu, this has come up before. I wanted to change this because native TLS implementation become awkward.
> https://mail.python.org/pipermail/python-dev/2008-August/081847.html
You didn't get answer to this old email :-( I suppose that you still want to fix PyThread_set_key_value()? |
|
Date |
User |
Action |
Args |
2013-11-28 21:37:27 | vstinner | set | recipients:
+ vstinner, tim.peters, pitrou, kristjan.jonsson, Arfrever, neologix |
2013-11-28 21:37:27 | vstinner | set | messageid: <1385674647.6.0.416637144703.issue19787@psf.upfronthosting.co.za> |
2013-11-28 21:37:27 | vstinner | link | issue19787 messages |
2013-11-28 21:37:27 | vstinner | create | |
|