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 asvetlov, pdxjohnny, r.david.murray, yselivanov, zach.ware
Date 2018-03-06.18:20:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
How is a separate base class better? :)

Having a default coroutine runner on the standard TestCase means all you have to do to add async tests is tack an `async` onto the front of your method definition, and everything just works as it always has.  Making it a separate base class means you have to know about that base class, what it's called, and remember to derive your test class from it.  If you accidentally add `async` to the front of a test method in a TestCase-derived test class, you get mostly-silent success with an easily-ignored warning about a coroutine not being awaited.
Date User Action Args
2018-03-06 18:20:07zach.waresetrecipients: + zach.ware, r.david.murray, asvetlov, yselivanov, pdxjohnny
2018-03-06 18:20:07zach.waresetmessageid: <>
2018-03-06 18:20:07zach.warelinkissue32972 messages
2018-03-06 18:20:07zach.warecreate