Message328892
| Author | dave-shawley |
|---|---|
| Recipients | Petter S, asvetlov, dave-shawley, njs, pdxjohnny, r.david.murray, yselivanov, zach.ware |
| Date | 2018-10-30.11:02:36 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1540897356.31.0.788709270274.issue32972@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hi all, I took a slightly different direction for adding async/await support to the unittest library. I summarized the approach that I took in a message to python-ideas (https://mail.python.org/pipermail/python-ideas/2018-October/054331.html) and a branch is available for preview in my fork of cpython (https://github.com/dave-shawley/cpython/pull/1). My question is whether I should reboot this bpo with my PR or create a new one since the implementation is different than what was already discussed? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-10-30 11:02:36 | dave-shawley | set | recipients: + dave-shawley, r.david.murray, njs, asvetlov, zach.ware, yselivanov, pdxjohnny, Petter S |
| 2018-10-30 11:02:36 | dave-shawley | set | messageid: <1540897356.31.0.788709270274.issue32972@psf.upfronthosting.co.za> |
| 2018-10-30 11:02:36 | dave-shawley | link | issue32972 messages |
| 2018-10-30 11:02:36 | dave-shawley | create | |