Tom Christie <t...@tomchristie.com> added the comment:
> 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...
```python
session = requests.Session()
session.get('https://example.com/')
```
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.)
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue36709>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
