[Python-Dev] Re: PEP 601: discussion-to discuss.python.org

2019-09-07 Thread Rob Cliffe via Python-Dev




On 04/09/2019 14:53:41, Victor Stinner wrote:

A litte bit more context.

PEP 601: "Forbid return/break/continue breaking out of finally"
https://www.python.org/dev/peps/pep-0601/

Abstract

This PEP proposes to forbid return, break and continue statements
within a finally suite where they would break out of the finally.
Their use in such a location silently cancels any active exception
being raised through the finally, leading to unclear code and possible
bugs.

Continue is currently not supported in a finally in Python 3.7 (due to
implementation issues) and the proposal is to not add support for it
in Python 3.8. For return and break the proposal is to deprecate their
use in Python 3.9, emit a compilation warning in Python 3.10 and then
forbid their use after that.

Victor
I can't make sense of this sentence in the PEP, I suspect there is a 
typo in it:


"Since this is the removal of a feature teaching users will be one by 
the raising of a SyntaxError if/when the forbidden feature is used."


Rob Cliffe

___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/LVGOPXZ57XU3E5CAZDPLX47ETPIIDOZ3/

---
This email has been checked for viruses by AVG.
https://www.avg.com



___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/KNYY4D6NL2DAG5ZGNDH3HPXQLSLGXLBT/


[Python-Dev] Re: PEP 601: discussion-to discuss.python.org

2019-09-07 Thread Jonathan Goble
On Sat, Sep 7, 2019, 8:59 AM Rob Cliffe via Python-Dev <
python-dev@python.org> wrote:

>
> I can't make sense of this sentence in the PEP, I suspect there is a
> typo in it:
>
> "Since this is the removal of a feature teaching users will be one by
> the raising of a SyntaxError if/when the forbidden feature is used."
>
> Rob Cliffe
>

Without context, I would guess that "one" is a typo for "done", which would
make much more sense in that spot in the sentence. A comma after the first
"feature" would also help in parsing the sentence.

>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/I3KSYGOCNFBXL2P7H2DQDPISZDZZGRXI/