Message313413
| Author | r.david.murray |
|---|---|
| Recipients | Petter S, asvetlov, pdxjohnny, r.david.murray, yselivanov, zach.ware |
| Date | 2018-03-08.00:45:15 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1520469915.79.0.467229070634.issue32972@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I agree with what Zach said in msg313352. I don't see how having a separate class affects the problem of what to use to run an async def test case. If "an AsyncTestCase should be enough" but "other frameworks will require a different test tool", why wouldn't support in TestCase for running the test under asyncio also be enough? I'm really not seeing what a separate class buys you. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-03-08 00:45:15 | r.david.murray | set | recipients: + r.david.murray, asvetlov, zach.ware, yselivanov, pdxjohnny, Petter S |
| 2018-03-08 00:45:15 | r.david.murray | set | messageid: <1520469915.79.0.467229070634.issue32972@psf.upfronthosting.co.za> |
| 2018-03-08 00:45:15 | r.david.murray | link | issue32972 messages |
| 2018-03-08 00:45:15 | r.david.murray | create | |