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 zach.ware
Recipients brett.cannon, chris.jerdonek, ezio.melotti, zach.ware
Date 2013-01-29.17:50:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359481811.94.0.214494559845.issue16968@psf.upfronthosting.co.za>
In-reply-to
Content
Right you are, Chris.  v4 has a comment added to regrtest.runtest_inner pointing back to this issue.

Also in v4, ReapedSuite has been moved to test.support.  At least one other test module (test_pydoc) uses the same idiom as test_concurrent_futures, and so could use this suite for the same effect.  Several others use at least one of reap_threads (or its component pieces) or reap_children in test_main, and I believe those could also use ReapedSuite for simplicity's sake.  Used in its current form, it shouldn't cause any issues other than perhaps an extra couple of function calls.
History
Date User Action Args
2013-01-29 17:50:12zach.waresetrecipients: + zach.ware, brett.cannon, ezio.melotti, chris.jerdonek
2013-01-29 17:50:11zach.waresetmessageid: <1359481811.94.0.214494559845.issue16968@psf.upfronthosting.co.za>
2013-01-29 17:50:11zach.warelinkissue16968 messages
2013-01-29 17:50:11zach.warecreate