Message 358419 - Python tracker

➜

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	brett.cannon, docs@python, gvanrossum, maggyero, mark.dickinson, ncoghlan
Date	2019-12-15.12:23:32
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1576412613.12.0.862152173434.issue39037@roundup.psfhosted.org>
In-reply-to

Content
It's a matter of historical timing: PEP 343 was written before try/except/finally was allowed, when try/finally and try/except were still distinct statements. However, PEP 341 was also accepted and implemented for Python 2.5, allowing for the modern try/except/finally form: https://docs.python.org/dev/whatsnew/2.5.html#pep-341-unified-try-except-finally

It's a matter of historical timing: PEP 343 was written before try/except/finally was allowed, when try/finally and try/except were still distinct statements.

However, PEP 341 was *also* accepted and implemented for Python 2.5, allowing for the modern try/except/finally form: https://docs.python.org/dev/whatsnew/2.5.html#pep-341-unified-try-except-finally

History
Date	User	Action	Args
2019-12-15 12:23:33	ncoghlan	set	recipients: + ncoghlan, gvanrossum, brett.cannon, mark.dickinson, docs@python, maggyero
2019-12-15 12:23:33	ncoghlan	set	messageid: <1576412613.12.0.862152173434.issue39037@roundup.psfhosted.org>
2019-12-15 12:23:33	ncoghlan	link	issue39037 messages
2019-12-15 12:23:32	ncoghlan	create