Message 301669 - Python tracker

➜

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	ncoghlan
Recipients	giampaolo.rodola, gregory.p.smith, ncoghlan, njs, vstinner, yselivanov
Date	2017-09-08.02:28:11
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1504837692.14.0.557083250889.issue31387@psf.upfronthosting.co.za>
In-reply-to

Content
As per Nathaniel's comments on issue 29988 and 31388, doing this robustly relies on: 1. the event loop being able to reliably guard itself and __aexit__ method implementations against interrupts (issue 31388) 2. "async with" statements ensuring that if the frame resumes after calling __aenter__, then it will also call __aexit__ (as was done for synchronous with statements in issue 29988)

As per Nathaniel's comments on issue 29988 and 31388, doing this robustly relies on:

1. the event loop being able to reliably guard itself and __aexit__ method implementations against interrupts (issue 31388)
2. "async with" statements ensuring that if the frame resumes after calling __aenter__, then it will also call __aexit__ (as was done for synchronous with statements in issue 29988)

History
Date	User	Action	Args
2017-09-08 02:28:12	ncoghlan	set	recipients: + ncoghlan, gregory.p.smith, vstinner, giampaolo.rodola, njs, yselivanov
2017-09-08 02:28:12	ncoghlan	set	messageid: <1504837692.14.0.557083250889.issue31387@psf.upfronthosting.co.za>
2017-09-08 02:28:12	ncoghlan	link	issue31387 messages
2017-09-08 02:28:11	ncoghlan	create