Some error messages changed and asyncio.async() has been deprecated and triggers many deprecation warnings, so using ensure_future() if present. Perhaps there is a better way to check for ensure_future()?
Coverage increased (+0.01%) to 91.582% when pulling 8f1745fb8a982ae55f6b21fb482c1cada49b3be3 on lyschoening:fix/python3.5 into 6c8904977215dc2c61f32de573ceaf9ef33b0717 on aio-libs:master.
Coverage increased (+0.02%) to 91.587% when pulling c3a72b23de9ef8795a5768f884ef5b15f770f438 on lyschoening:fix/python3.5 into 6c8904977215dc2c61f32de573ceaf9ef33b0717 on aio-libs:master.
Coverage increased (+0.02%) to 91.587% when pulling b5bc55e99c99b266fbf41d0d9cc12b8cf1c63853 on lyschoening:fix/python3.5 into 6c8904977215dc2c61f32de573ceaf9ef33b0717 on aio-libs:master.
Some error messages changed and
asyncio.async()
has been deprecated and triggers many deprecation warnings, so usingensure_future()
if present. Perhaps there is a better way to check for ensure_future()?