Message 361269 - 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	mdk
Recipients	mdk
Date	2020-02-03.08:21:12
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1580718072.8.0.280721133758.issue39534@roundup.psfhosted.org>
In-reply-to

Content
According to [1][2] the documentation about return in finally statement is missleading in [3]. It currently states: > If a finally clause includes a return statement, the finally clause’s return statement will execute before, and instead of, the return statement in a try clause. I would prefer speaking about returned values instead of statements executed, I think it would clarify the point. [1]: https://mail.python.org/archives/list/docs@python.org/message/LBMO47JSDPKFKLYR25HAKD7A76D5IHWI/ [2]: https://stackoverflow.com/questions/59639733/python-docs-have-misleading-explanation-of-return-in-finally [3]: https://docs.python.org/3.7/tutorial/errors.html#defining-clean-up-actions

According to [1][2] the documentation about return in finally statement is missleading in [3].

It currently states:

> If a finally clause includes a return statement, the finally clause’s return statement will execute before, and instead of, the return statement in a try clause.

I would prefer speaking about returned values instead of statements executed, I think it would clarify the point.


[1]: https://mail.python.org/archives/list/docs@python.org/message/LBMO47JSDPKFKLYR25HAKD7A76D5IHWI/
[2]: https://stackoverflow.com/questions/59639733/python-docs-have-misleading-explanation-of-return-in-finally
[3]: https://docs.python.org/3.7/tutorial/errors.html#defining-clean-up-actions

History
Date	User	Action	Args
2020-02-03 08:21:12	mdk	set	recipients: + mdk
2020-02-03 08:21:12	mdk	set	messageid: <1580718072.8.0.280721133758.issue39534@roundup.psfhosted.org>
2020-02-03 08:21:12	mdk	link	issue39534 messages
2020-02-03 08:21:12	mdk	create