aiohttp 3.5 release

Created on 8 Nov 2018 · 7Comments · Source: aio-libs/aiohttp

We are close to aiohttp 3.5.

My plan is:

Review pending PRs: #3205 #3324 #3362 #3365
Make connector.close() returning a future as a step to converting it to async function in aiohttp 4.0
Reformat code with black

Please feel free to add missing things in comments

enhancement

Source

asvetlov

👍2 🎉1

Most helpful comment

Hi. I'd like to publish aiohttp 3.5 on this or next week (but defnitely in this year).
It was a long run, 3.4 was released 4 months ago.

If some bugs will be not fixed -- that's satisfactory, we can make a bugfix release later.

asvetlov on 17 Dec 2018

👍3

All 7 comments

GitMate.io thinks possibly related issues are https://github.com/aio-libs/aiohttp/issues/3024 (aiohttp 3.3 release), https://github.com/aio-libs/aiohttp/issues/58 (aiohttp.HttpClient), https://github.com/aio-libs/aiohttp/issues/2224 (aiohttp.TCPConnector()), https://github.com/aio-libs/aiohttp/issues/1604 (aiohttp 1.3.0 sdist ?), and https://github.com/aio-libs/aiohttp/issues/467 (Failed building wheel for aiohttp on Python 3.5.0rc1).

aio-libs-bot on 8 Nov 2018

3364 - looks like useful fix, there is PR.

3380 - feels like we have some tricky bug. Still in lazy debug process.

kxepal on 8 Nov 2018

Hm, I think we should include a fix for adding closing/closed checks to aiohttp.web.WebSocketResponse's send_xxx() methods as I mentioned in the gitter channel.
I will make an issue -- #3391.