This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author anthonybaxter
Date 2004-05-26.15:43:29
SpamBayes Score
Marked as misclassified
Logged In: YES 

This will not be in 2.3.4, as I've already stated.

a) We've already cut the release candidate, and the final
release is less than 12 hours away
b) this is a high-risk patch -- anything in the area of
threads and signals is very risky.

Here's how it should go forward:

First, the trunk should be patched. This fix can then be in
Once we're through to 2.4 final, we'll know whether the fix
is good enough for the 2.3 series.
Finally, after 2.4 final comes out, there will be a 2.3.5.
This fix can be in that, assuming it's fine in 2.4.

Date User Action Args
2007-08-23 14:14:07adminlinkissue756924 messages
2007-08-23 14:14:07admincreate