Message351917
I may be wrong, but I believe that the bug requires using the C API (not just pure Python code). This is because Python-level lock objects have their own lifetime, and should never be freed while another thread is in PyThread_release_lock() with them.
Nevertheless, the example shows that using this C API "correctly" is very hard. Most direct users of the C API could run into the same problem in theory. |
|
Date |
User |
Action |
Args |
2019-09-11 14:57:08 | arigo | set | recipients:
+ arigo, tim.peters, loewis, rhettinger, terry.reedy, beazley, paul.moore, shihao, ronaldoussoren, pitrou, scoder, kristjan.jonsson, vstinner, techtonik, jyasskin, tim.golden, benjamin.peterson, ned.deily, r.david.murray, brian.curtin, flox, dabeaz, torsten, ysj.ray, python-dev, sbt, navytux |
2019-09-11 14:57:08 | arigo | set | messageid: <1568213828.91.0.92668672123.issue38106@roundup.psfhosted.org> |
2019-09-11 14:57:08 | arigo | link | issue38106 messages |
2019-09-11 14:57:08 | arigo | create | |
|