➜

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 yselivanov
Recipients asvetlov, gvanrossum, ncoghlan, python-dev, scoder, vstinner, yselivanov
Date 2015-05-13.05:10:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431493843.97.0.101515267068.issue24017@psf.upfronthosting.co.za>
In-reply-to
Content 
> Is there are a specific reason this implicit exception handler can't be decomposed and implemented using the same opcodes as are used to implement explicit exception handlers?

I don't think it's possible to replace ASYNC_WITH_CLEANUP_EXCEPT opcode with some combination of existing opcodes.

What might be possible is to implement 'async with' without using WITH_CLEANUP_* opcodes at all.  Let me try that.
History
Date User Action Args
2015-05-13 05:10:44yselivanovsetrecipients: + yselivanov, gvanrossum, ncoghlan, scoder, vstinner, asvetlov, python-dev
2015-05-13 05:10:43yselivanovsetmessageid: <1431493843.97.0.101515267068.issue24017@psf.upfronthosting.co.za>
2015-05-13 05:10:43yselivanovlinkissue24017 messages
2015-05-13 05:10:43yselivanovcreate