In Lib\test\test_decimal.py, attached is a bugfix for two bugs:
1) If the thfunc2 actually fails, then its thread will throw an
exception and never set the Events that thfunc1 is waiting for; thus,
thfunc1 never returns, causing the whole unittest to hang.
2) DecimalUseOfContextTest.test_threading should wait on both finish1
and finish2 (instead of waiting on finish1 twice).

This is a minor annoyance that's tripped me up before as well.  Only 
minor, since it only happens when there's something wrong with 
decimal.py.

The patch looks sound;  I've attached a regenerated version of it 
against the trunk.  (Note that the finish1 -> finish2 bug was already 
fixed in the trunk.)  I think it should be applied, and probably 
backported to 2.5 as well.

Jared, thanks for the report and the patch!  I'm curious to know how you 
encountered this;  if test_decimal is failing for a good reason, then 
there may be a Decimal bug to be fixed.

I ran into this bug because I created a context manager in one of my own
projects, and the regression tests in test_decimal looked like a good
start for my own regression tests... when some recent changes broke MY
code, I found the test bug too and realized that the test_decimal file
had the same problem. So, I figured I'd share the wealth :)

Commited in r61731.

Thank you both!