Message131717
> Ok, good idea, I will do that. I think that I will write it in the
> function comment, something like: "This function is signal safe".
Done in 6685691dfcbd3644feffcb197491bce3168ff5de (git SHA-1)
While checking the usage of signal safe functions, I found a bug: dumpbacktrace_later() signal handler called Py_CLEAR() which is far from being signal safe. I tried to replace it be a pending call, but Py_AddPendingCall() doesn't look to be signal safe. So I just removed the call. cancel_dumpbacktrace_later() is already documented as being required to clear the reference to the file.
> > - within tests.py, ...
> Ok, I will try to find better names.
Done in db99e17dea187bec4248aca9fc81f673d88dec93. I documented methods and renamed some of them. |
|
Date |
User |
Action |
Args |
2011-03-22 01:32:48 | vstinner | set | recipients:
+ vstinner, pitrou, Arfrever, dmalcolm |
2011-03-22 01:32:47 | vstinner | set | messageid: <1300757567.99.0.927560338617.issue11393@psf.upfronthosting.co.za> |
2011-03-22 01:32:47 | vstinner | link | issue11393 messages |
2011-03-22 01:32:47 | vstinner | create | |
|