Address breaking change introduced in aiohttp==3.9.2#1081
Address breaking change introduced in aiohttp==3.9.2#1081thehesiod merged 3 commits intoaio-libs:masterfrom
aiohttp==3.9.2#1081Conversation
3b7b25c to
99b9244
Compare
99b9244 to
df59f9c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1081 +/- ##
==========================================
- Coverage 86.33% 86.28% -0.06%
==========================================
Files 62 62
Lines 5913 5913
==========================================
- Hits 5105 5102 -3
- Misses 808 811 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Seems like they addressed this in 3.9.3 aio-libs/aiohttp#8098 |
Indeed, still we should cease using the deprecated |
perhaps of note is that #749 (which I've been slowly chugging away on) wants to replace aiohttp with httpx, so there might not be a very long future for aiohttp. |
|
@thehesiod: This PR builds on #1077. Maybe we should first finish that PR? |
79595c4 to
a9787f3
Compare
a9787f3 to
cb6bfed
Compare
cb6bfed to
fd2ff56
Compare
|
CI doesn't allow for two releases dated the same in CHANGES.txt :-( |
|
will fix test here, one sec |
fix test
Description of Change
aiohttp==3.9.2introduces a change in handling SSL/TLS-related arguments that breaks our code. This PR applies currentaiohttpbest-practices to SSL/TLS-related arguments.Assumptions
aiohttpwas bumped to prevent regressions with our updated code andaiohttp<3.9.2.Checklist for All Submissions
Checklist when updating botocore and/or aiohttp versions