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

Drop Python 3.6 support #5278

Merged
merged 6 commits into from
Nov 23, 2020
Merged

Drop Python 3.6 support #5278

merged 6 commits into from
Nov 23, 2020

Conversation

asvetlov
Copy link
Member

Python 3.6 is close to EOL, aiohttp 4.0 is not released yet.
Dropping Python 3.6 for aiohttp 4.0 allows dropping a bunch of backward compatibility shims.

@psf-chronographer psf-chronographer bot added the bot:chronographer:provided There is a change note present in this PR label Nov 23, 2020
@@ -5,8 +5,8 @@

from setuptools import Extension, setup

if sys.version_info < (3, 6):
raise RuntimeError("aiohttp 4.x requires Python 3.6+")
if sys.version_info < (3, 7):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: I believe that with this change, we'll be able to migrate most of setup.py to setup.cfg since CPython 3.7.0 ships pip==10.0.1 and setuptools==39.0.1.
setup.cfg support was added in setuptools 30.3.0 and Requires-Python support has been added in pip 9.0.0.
Meaning that it's virtually impossible to hit this condition under the supported Python version. Add the platform wheels that we ship and you'll see that in 99% of cases users won't even run setup.py.

P.S. This is a topic for a separate PR, I just wanted to post some thoughts here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I support the proposal (in a separate PR) but don't want to apply the change myself.
Regarding binary wheels -- the case number 1 when people build from tarball are Alpine Linux users.

@webknjaz
Copy link
Member

Looks like you also need to drop 3.6 from GHA

@asvetlov
Copy link
Member Author

Looks like you also need to drop 3.6 from GHA

Ooops. Done

@codecov
Copy link

codecov bot commented Nov 23, 2020

Codecov Report

Merging #5278 (2127b3a) into master (e65f1a9) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5278      +/-   ##
==========================================
- Coverage   97.53%   97.52%   -0.01%     
==========================================
  Files          43       43              
  Lines        8818     8784      -34     
  Branches     1418     1410       -8     
==========================================
- Hits         8601     8567      -34     
- Misses        102      103       +1     
+ Partials      115      114       -1     
Flag Coverage Δ
unit 97.41% <100.00%> (+0.04%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
aiohttp/connector.py 96.48% <100.00%> (-0.32%) ⬇️
aiohttp/cookiejar.py 98.78% <100.00%> (+<0.01%) ⬆️
aiohttp/helpers.py 96.78% <100.00%> (+0.22%) ⬆️
aiohttp/pytest_plugin.py 97.45% <100.00%> (-0.05%) ⬇️
aiohttp/resolver.py 93.18% <100.00%> (ø)
aiohttp/web.py 99.14% <100.00%> (-0.01%) ⬇️
aiohttp/web_protocol.py 92.28% <100.00%> (ø)
aiohttp/web_runner.py 97.76% <100.00%> (-0.01%) ⬇️
aiohttp/web_server.py 94.28% <100.00%> (-0.16%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e65f1a9...2127b3a. Read the comment docs.

@asvetlov asvetlov merged commit 0f0c375 into master Nov 23, 2020
@asvetlov asvetlov deleted the drop-py3.6 branch November 23, 2020 20:08
commonism pushed a commit to commonism/aiohttp that referenced this pull request Apr 27, 2021
commonism pushed a commit to commonism/aiohttp that referenced this pull request Apr 27, 2021
bdraco pushed a commit that referenced this pull request Jul 17, 2024
(cherry picked from commit 0f0c375)
bdraco pushed a commit that referenced this pull request Jul 17, 2024
(cherry picked from commit 0f0c375)
bdraco pushed a commit that referenced this pull request Jul 17, 2024
(cherry picked from commit 0f0c375)
bdraco pushed a commit that referenced this pull request Jul 17, 2024
(cherry picked from commit 0f0c375)
bdraco added a commit that referenced this pull request Jul 17, 2024
Co-authored-by: Andrew Svetlov <andrew.svetlov@gmail.com>
@bdraco bdraco mentioned this pull request Jul 30, 2024
1 task
bdraco added a commit that referenced this pull request Jul 31, 2024
bdraco added a commit that referenced this pull request Aug 1, 2024
Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <sviat@redhat.com>
patchback bot pushed a commit that referenced this pull request Aug 1, 2024
Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <sviat@redhat.com>
(cherry picked from commit e48acaf)
patchback bot pushed a commit that referenced this pull request Aug 1, 2024
Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <sviat@redhat.com>
(cherry picked from commit e48acaf)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:provided There is a change note present in this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants