-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aiohttp 3.1 release #2829
Comments
no rush! we have the work-around for now :) I'm guesstimating it will take us a couple more months to switch to aiohttp 3.x (we have a lot of services that depend in aiohttp now so things keep on getting harder to upgrade). |
I'm working on #2756 to support |
@achimnol nice! |
Done |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs. |
We have about 20 new features according to
CHANGES
folder.More than a month of development.
Let's make 3.1 release.
Release fast, release early!
I'd like to finish
app.add_routes()
in server docs everywhere Useapp.add_routes()
in server docs everywhere #2830Rewrite server docs to get rid of mentioning
app.router.add_get()
and family in Quickstart / Advanced Usage sections. Replacing them byapp.add_routes()
.Unfortunately the list of pending issues is still big (@thehesiod I remember about client timeouts, sure) but I see no reason to postpone the release.
We can implement pending tasks in backward compatible manner in aiohttp 3.2.
The release date is not scheduled yet, if you want to hop on the bus -- please hurry up (and write about your striving in a comment). I'll update blocker issues list.
The text was updated successfully, but these errors were encountered: