-
-
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.5 support #3588
Comments
Personally, I'm pro dropping support for python 3.5. Maybe elegant, maybe very confusing that aiohttp==3.5 is the last version that supports python 3.5. 😄 |
Also, if we dropped 3.5, we could swap from using If we wanted strict type checks we could use
dataclasses are the pythonic way to do, are much faster and should play nicely with type hinting. I'd be happy to do this work if agreed. |
I vote FOR removal. Build system must check Python version for those who will try to build new aiohttp using old Python. Also I vote for removal of different obsolete wrappers not connected with Python > 3.5. |
+1 to drop Python 3.5 support. |
I see problems with Regarding Python 3.5 drop: Debian Stretch is shipped with Python 3.5. Perhaps I have to post my wishlist on the tracker. I'm on a business trip now and have very limited capacity for this month. That's why I cannot spend too much time on aiohttp right now, unfortunately. I don't give up but have a limited capacity. It can shift aiohttp 4.0 release date. |
Ok. Please could you give more details on the move from |
BTW, |
I don't know if a decision was made on dropping python 3.5 support, but it seems like it effectively is dropped in aiohttp==3.5.4
|
aiohttp 3.x requires Python 3.5.3+ |
Python 3.5 support is dropped |
@socketpair asked me about 3.5 LTS policy: #3568 (comment)
I see the rule is not pronounced yet.
Let me fix this point of misunderstanding.
4.0
. Please consider it as housekeeping release. The main point is to clean up the library to allow future awesome changes later.3.5
andmaster
branches will diverge too much -- the support of3.5
will be dropped.Thoughts? Comments? Proposals?
The text was updated successfully, but these errors were encountered: