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-30.14:00:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559224841.64.0.159073330265.issue36709@roundup.psfhosted.org>
In-reply-to
Content
Right, and `requests` *does* provide both those styles.

The point more being that *not* having closed the transport at the point of exit shouldn't end up raising a hard error. It doesn't raise errors in sync-land, and it shouldn't do so in async-land.

Similarly, we wouldn't expect an open file resource to cause errors to be raised at the point of exit.
History
Date User Action Args
2019-05-30 14:00:41tomchristiesetrecipients: + tomchristie, christian.heimes, asvetlov, yselivanov
2019-05-30 14:00:41tomchristiesetmessageid: <1559224841.64.0.159073330265.issue36709@roundup.psfhosted.org>
2019-05-30 14:00:41tomchristielinkissue36709 messages
2019-05-30 14:00:41tomchristiecreate