Skip to content
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

Closed
2 of 3 tasks
asvetlov opened this issue Mar 13, 2018 · 6 comments
Closed
2 of 3 tasks

aiohttp 3.1 release #2829

asvetlov opened this issue Mar 13, 2018 · 6 comments
Labels
Milestone

Comments

@asvetlov
Copy link
Member

asvetlov commented Mar 13, 2018

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

Rewrite server docs to get rid of mentioning app.router.add_get() and family in Quickstart / Advanced Usage sections. Replacing them by app.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.

@thehesiod
Copy link
Contributor

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).

@asvetlov
Copy link
Member Author

I've shrinked ambitious UrlDispatcher refactoring #2766 to just docs update #2830

@achimnol
Copy link
Member

I'm working on #2756 to support url_for as well. PR coming soon!

@asvetlov
Copy link
Member Author

@achimnol nice!

@asvetlov asvetlov added this to the 3.1 milestone Mar 17, 2018
@asvetlov
Copy link
Member Author

Done

@lock
Copy link

lock bot commented Oct 28, 2019

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.
If you feel like there's important points made in this discussion, please include those exceprts into that [new issue].
[new issue]: https://github.com/aio-libs/aiohttp/issues/new

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants