PEP601: Add rejection notice (#1173)
This commit is contained in:
parent
bd03d819a1
commit
8400ea55ac
16
pep-0601.txt
16
pep-0601.txt
|
@ -3,12 +3,24 @@ Title: Forbid return/break/continue breaking out of finally
|
|||
Author: Damien George, Batuhan Taskaya
|
||||
Sponsor: Nick Coghlan
|
||||
Discussions-To: https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239
|
||||
Status: Draft
|
||||
Status: Rejected
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 26-Aug-2019
|
||||
Python-Version: 3.8
|
||||
Post-History: 26-Aug-2019
|
||||
Post-History: 26-Aug-2019 23-Sep-2019
|
||||
Resolution: https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/32
|
||||
|
||||
Rejection Note
|
||||
==============
|
||||
|
||||
This PEP was rejected by the Steering Council by a vote of 4/4.
|
||||
|
||||
Guido's arguments for rejecting the PEP are: "it seems to me that most languages
|
||||
implement this kind of construct but have style guides and/or linters that
|
||||
reject it. I would support a proposal to add this to PEP 8", and "I note that
|
||||
the toy examples are somewhat misleading – the functionality that may be useful
|
||||
is a conditional return (or break etc.) inside a finally block.".
|
||||
|
||||
Abstract
|
||||
========
|
||||
|
|
Loading…
Reference in New Issue