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 John Belmonte
Recipients John Belmonte, asvetlov, xtreak, yselivanov
Date 2019-06-25.11:35:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561462522.77.0.767552862828.issue37398@roundup.psfhosted.org>
In-reply-to
Content
PerfTimer is a reusable, non-reentrant context manager implemented as a class.

There are already use cases of ContextDecorator described in the contextlib documentation, such as the track_entry_and_exit logger.  What reason would you have for such context managers to *not* wrap async functions properly?
History
Date User Action Args
2019-06-25 11:35:22John Belmontesetrecipients: + John Belmonte, asvetlov, yselivanov, xtreak
2019-06-25 11:35:22John Belmontesetmessageid: <1561462522.77.0.767552862828.issue37398@roundup.psfhosted.org>
2019-06-25 11:35:22John Belmontelinkissue37398 messages
2019-06-25 11:35:22John Belmontecreate