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 Petter S
Recipients Petter S, asvetlov, pdxjohnny, r.david.murray, yselivanov, zach.ware
Date 2018-03-06.19:14:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1520363690.79.0.467229070634.issue32972@psf.upfronthosting.co.za>
In-reply-to
Content
It's good to see others with the same idea as me. I just wrote https://github.com/python/cpython/pull/6005/commits/4d7e1837f235687c875e985e97701609fc1ac458 .

In my opinion, there is no need for another test class. I completely agree with Zachary Ware that the current TestCase class is more or less broken (or at least easily misused) with respect to coroutines.

Fixing TestCase would not break existing code. The customization of event loop would not be hard to add.
History
Date User Action Args
2018-03-06 19:14:50Petter Ssetrecipients: + Petter S, r.david.murray, asvetlov, zach.ware, yselivanov, pdxjohnny
2018-03-06 19:14:50Petter Ssetmessageid: <1520363690.79.0.467229070634.issue32972@psf.upfronthosting.co.za>
2018-03-06 19:14:50Petter Slinkissue32972 messages
2018-03-06 19:14:50Petter Screate