➜

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 brian.curtin
Recipients Pablo.Bitton, abbot, astrand, belopolsky, brian.curtin, dmalcolm, filippo, gd2shoe, giampaolo.rodola, guettli, matthieu.labbe, orsenthil, pitrou, r.david.murray, ragnar, rnk, srid, tim.golden
Date 2010-08-09.14:23:49
SpamBayes Score 0.0004224092
Marked as misclassified No
Message-id <1281363831.44.0.209707972383.issue5673@psf.upfronthosting.co.za>
In-reply-to
Content 
"I've been using the subprocess-timeout-v5.patch patch with 2.x. Isn't that version supposed to work with 2.x?"

Actually, yes, so I was wrong at first. The v5 patch will work with 2.x, but that's not the most up to date or correct patch. This feature will only be going into the py3k branch (aka 3.2), so issues with prior patches on 2.x aren't as valuable as those possibly found on the latest patch on 3.x.
History
Date User Action Args
2010-08-09 14:23:52brian.curtinsetrecipients: + brian.curtin, guettli, astrand, belopolsky, orsenthil, pitrou, ragnar, giampaolo.rodola, tim.golden, abbot, gd2shoe, r.david.murray, rnk, srid, matthieu.labbe, dmalcolm, filippo, Pablo.Bitton
2010-08-09 14:23:51brian.curtinsetmessageid: <1281363831.44.0.209707972383.issue5673@psf.upfronthosting.co.za>
2010-08-09 14:23:49brian.curtinlinkissue5673 messages
2010-08-09 14:23:49brian.curtincreate