Message349693
| 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 |
<1565787738.64.0.534975356011.issue37830@roundup.psfhosted.org> |
| In-reply-to |
|
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2019-08-14 13:02:18 | ncoghlan | set | recipients:
+ ncoghlan, vstinner, eric.smith, ethan.furman, lukasz.langa, Mark.Shannon, serhiy.storchaka, ppperry, pablogsal, xtreak, BTaskaya |
| 2019-08-14 13:02:18 | ncoghlan | set | messageid: <1565787738.64.0.534975356011.issue37830@roundup.psfhosted.org> |
| 2019-08-14 13:02:18 | ncoghlan | link | issue37830 messages |
| 2019-08-14 13:02:18 | ncoghlan | create | |
|