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 BTaskaya, Mark.Shannon, eric.smith, ethan.furman, lukasz.langa, ncoghlan, pablogsal, ppperry, serhiy.storchaka, vstinner, xtreak
Date 2019-08-14.13:02:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Even though it doesn't fully resolve this crash, I'd still like us to consider reverting the change to allow "continue" in try/finally blocks.

It doesn't seem to have a compelling practical motivation behind it (beyond the fact that it's nice not to impose arbitrary restriction on users), and even if it's feasible in CPython now, it still creates a non-trivial amount of work for other Python implementations that are trying to remain consistent with what CPython allows.
Date User Action Args
2019-08-14 13:02:18ncoghlansetrecipients: + ncoghlan, vstinner, eric.smith, ethan.furman, lukasz.langa, Mark.Shannon, serhiy.storchaka, ppperry, pablogsal, xtreak, BTaskaya
2019-08-14 13:02:18ncoghlansetmessageid: <>
2019-08-14 13:02:18ncoghlanlinkissue37830 messages
2019-08-14 13:02:18ncoghlancreate