Repository navigation
Deprecate TCPConnector ssl - #13829
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #13829 +/- ##
==========================================
- Coverage 99.04% 99.03% -0.01%
==========================================
Files 135 135
Lines 51378 51399 +21
Branches 2693 2694 +1
==========================================
+ Hits 50885 50904 +19
- Misses 371 372 +1
- Partials 122 123 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
|
Comments Outside DiffThese findings sit on lines the diff does not cover, so they could not be posted inline. Each one leaves this list once its file changes.
|
Merging this PR will not alter performance
Comparing Footnotes
|
Upstream deprecated TCPConnector's ssl parameter in favor of ClientSession/per-request ssl. Both still resolve to the same module-level _SSL_CONTEXT_VERIFIED default, so kept the truststore note alongside the new deprecation notice instead of dropping either.
…nector ssl) That commit stopped constructing a TCPConnector in test_static_file_ssl, passing ssl straight to aiohttp_client instead, so the leftover conn.aclose() teardown call had nothing left to close. Dropped it. It also added three new tests that call conn.close() as plain teardown, not intentionally exercising the deprecation. Since BaseConnector.close() now warns, filterwarnings=error turned that into a failure. Switched those three to aclose(), matching the same fix already applied to every other internal call site in this rename.
No description provided.