[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Vladimir Ryabtsev added the comment: The issue won't be fixed, but other useful changes applied. -- resolution: -> wont fix stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Carol Willing added the comment: New changeset 3f9fe23c05280dc5736c07bb0e968cdaf8c503d0 by Vladimir in branch 'master': bpo-42179: Clarify exception chaining (GH-23160) https://github.com/python/cpython/commit/3f9fe23c05280dc5736c07bb0e968cdaf8c503d0 --

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Vladimir Ryabtsev added the comment: All right, you won. I hope beginner users will be happy :) I removed my proposal paragraph about __cause__ and __context__ and kept only changes about exception type (https://bugs.python.org/issue42179#msg380435). -- _

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Inada Naoki added the comment: >> 1. Such understanding of a tutorial is debatable. Tutorial is just a >> material for learning written with some system in mind, which is more >> interesting to read than dry reference material. A tutorial, generally >> dpeaking, may be both for beginners and

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

miss-islington added the comment: New changeset e74fb2d7666eea43ad738528a565bb56bc88c28d by Miss Islington (bot) in branch '3.9': bpo-42179: Doc/tutorial: Remove mention of __cause__ (GH-23162) https://github.com/python/cpython/commit/e74fb2d7666eea43ad738528a565bb56bc88c28d -- ___

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +22086 pull_request: https://github.com/python/cpython/pull/23173 ___ Python tracker _

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Inada Naoki added the comment: New changeset bde33e428d5b5f88ec7667598fd27d1091840537 by Inada Naoki in branch 'master': bpo-42179: Doc/tutorial: Remove mention of __cause__ (GH-23162) https://github.com/python/cpython/commit/bde33e428d5b5f88ec7667598fd27d1091840537 --

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Change by Zachary Ware : Removed file: https://bugs.python.org/file49575/Cellular-Z 20200909 14:25:47 SLOT1.CSV ___ Python tracker ___ ___

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Change by David Martinez : Added file: https://bugs.python.org/file49575/Cellular-Z 20200909 14:25:47 SLOT1.CSV ___ Python tracker ___ ___

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Carol Willing added the comment: Thanks Vladimir for raising the issue, and Inada-san and Eric for following up on it. I recommend the following: - merge PR-23162 including its reference to builtin exceptions - after merge of PR-23162, reworking PR-23160 to provide a brief note about __cause

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Vladimir Ryabtsev added the comment: Also, the choice of the exception type in the example looks not very apt: you raise "IOError" but the traceback message says "OSError" (which is due to strange design decision "IOError = OSError"). For the tutorial, I would choose an exception that does n

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Vladimir Ryabtsev added the comment: We have automatic chaining, so you don't need to use "from X" unless you want to have some control on the traceback message. Even without knowing of this syntax (and without using "from exc"), a user will get a traceback message similar to what is shown i

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Éric Araujo added the comment: I prefer the patch by Inada-san! >> Describing the default behavior and "from None" is enough for new users > Strange that you think that "from None" is more useful for beginners than > these special attributes. Doesn’t feel strange to me: `raise Exc from exc`

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Vladimir Ryabtsev added the comment: > I can not find confusion caused by this tutorial section Inada, have you read the very first message in this ticket? It explains why this wording may cause confusion (and it did in me), and describes the problem part. A link for your convenience: https:

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Change by Inada Naoki : -- pull_requests: +22074 pull_request: https://github.com/python/cpython/pull/23162 ___ Python tracker ___ _

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Inada Naoki added the comment: > 1. Such understanding of a tutorial is debatable. Tutorial is just a material > for learning written with some system in mind, which is more interesting to > read than dry reference material. A tutorial, generally dpeaking, may be both > for beginners and for

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Vladimir Ryabtsev added the comment: 1. Such understanding of a tutorial is debatable. Tutorial is just a material for learning written with some system in mind, which is more interesting to read than dry reference material. A tutorial, generally dpeaking, may be both for beginners and for pr

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Inada Naoki added the comment: Please note that tutorial is a tutorial. It is document to help new user who are learning Python. Do you believe special attributes like __cause__ and __contexts__ are really worth to teach for tutorial readers? Generally speaking, I think we should *reduce* so

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

Change by Vladimir Ryabtsev : -- keywords: +patch pull_requests: +22072 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23160 ___ Python tracker __

[issue42179] Clarify chaining exceptions in tutorial/errors.rst

New submission from Vladimir Ryabtsev : A new section has been added to the page as a result of https://bugs.python.org/issue37826. The change: https://github.com/python/cpython/commit/dcfe111eb5602333135b8776996332a8dcf59392 The wording it uses (in the beginning of section 8.5), defines chai