# PEP 601: Forbid return/break/continue breaking out of finally

**URL:** <https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239>\
**Category:** PEPs\
**Created:** [September 3, 2019, 1:12pm UTC](https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239 "2019-09-03T13:12:07Z")\
**Posts on this page:** 4\
**Page:** 3

<div class="post-metadata">

**Author:** ![dpgeorge](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/dpgeorge/32/1351_2.png) [@dpgeorge](https://discuss.python.org/u/dpgeorge)\
**Post date:** [September 23, 2019, 3:09am UTC](https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/41 "2019-09-23T03:09:32Z")

</div>

I have made PRs to update PEP 601 and PEP 8, see [https://github.com/python/peps/pull/1173](https://github.com/python/peps/pull/1173) and [https://github.com/python/peps/pull/1174](https://github.com/python/peps/pull/1174) respectively.

---

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [September 23, 2019, 2:17pm UTC](https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/42 "2019-09-23T14:17:17Z")

</div>

Thanks, I approved and merged both.

(OT: There’s never a need to squash commits, we do that when we press the “Squash and Merge” button on GitHub. Squashing is actually counterproductive for the review, as is force-pushing amended commits – it can confuse the reviewer.)

---

<div class="post-metadata">

**Author:** ![aeros](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/aeros/32/4140_2.png) [@aeros](https://discuss.python.org/u/aeros)\
**Post date:** [September 24, 2019, 6:47am UTC](https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/43 "2019-09-24T06:47:19Z")

</div>

> [@guido](#):
>
> (OT: There’s never a need to squash commits, we do that when we press the “Squash and Merge” button on GitHub. Squashing is actually counterproductive for the review, as is force-pushing amended commits – it can confuse the reviewer.)

I’ve said something along the same lines a few times in PRs when the authors have asked if they should squash their commits, but it’s useful to know the official stance. Thanks for mentioning it.

---

<div class="post-metadata">

**Author:** ![dpgeorge](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/dpgeorge/32/1351_2.png) [@dpgeorge](https://discuss.python.org/u/dpgeorge)\
**Post date:** [October 4, 2019, 1:22pm UTC](https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/44 "2019-10-04T13:22:30Z")

</div>

FWIW, I’ve now fixed continue within a finally in MicroPython, see [https://github.com/micropython/micropython/pull/5154](https://github.com/micropython/micropython/pull/5154)

[Previous page](https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239.md?page=2)