Zachary Ware <zachary.w...@gmail.com> added the comment: Ok, Yury clarified a few points before I got my message submitted there, so some of my last message may be a bit misguided. In particular, the problems with just using `asyncio.run` are clearer to me now.
To give my answers to Yury's open questions: - We should have an async setUpClass capability, one way or another. - I would say event loop per class. If someone really needs event loop per method, they can create separate classes per method. It's ugly, but effective. - We should have an async setUp capability. Maybe we could add a helper method to be called from setUp rather than adding a whole new asyncSetUp into the protocol? That eliminates the problem of which goes first. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32972> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
