This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tomchristie
Recipients asvetlov, christian.heimes, tomchristie, yselivanov
Date 2019-05-28.14:04:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> From my understanding, the correct code should close all transports and wait for their connection_lost() callbacks before closing the loop.

Ideally, yes, although we should be able to expect that an SSL connection that hasn't been gracefully closed wouldn't loudly error on teardown like that.

In standard sync code, the equivelent would running something like this...

session = requests.Session()

We wouldn't expect a traceback to be raised on exiting. (Even though the user *hasn't* explicitly closed the session, and even though a keep alive SSL connection will be open at the point of exit.)
Date User Action Args
2019-05-28 14:04:20tomchristiesetrecipients: + tomchristie, christian.heimes, asvetlov, yselivanov
2019-05-28 14:04:19tomchristiesetmessageid: <>
2019-05-28 14:04:19tomchristielinkissue36709 messages
2019-05-28 14:04:19tomchristiecreate