Comment 17 for bug 1101404

Ew, apparently this was fixed upstream in Python 2.7, but 2.6 didn't get the fix. I'm not really sure there's anything we can do about that here - the only solution I think is likely to be accepted is to get the fix backported to py26, but I'm not sure how feasible that is either.