Message80209
| Author |
kristjan.jonsson |
| Recipients |
amaury.forgeotdarc, kristjan.jonsson, loewis, mhammond |
| Date |
2009年01月19日.21:06:36 |
| SpamBayes Score |
0.0070681255 |
| Marked as misclassified |
No |
| Message-id |
<1232399205.66.0.885693952438.issue4804@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Here is what I think is a better attempt at the selective-disabling. I
did away with the messy macros and added a function in errors.c. This
maintans a global 'level' variable, implicitly guarded by the GIL. Now
only the thread that first enters a guarded block will set the hendler,
and the thread that is last to leave will reset it. This should
guarantee that between the two macros, our custom handler is set, and
that no thread pulls the rug from underneath another. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年01月19日 21:06:47 | kristjan.jonsson | set | recipients:
+ kristjan.jonsson, loewis, mhammond, amaury.forgeotdarc |
| 2009年01月19日 21:06:45 | kristjan.jonsson | set | messageid: <1232399205.66.0.885693952438.issue4804@psf.upfronthosting.co.za> |
| 2009年01月19日 21:06:44 | kristjan.jonsson | link | issue4804 messages |
| 2009年01月19日 21:06:43 | kristjan.jonsson | create |
|