[issue29762] Use "raise from None"

Change by Pablo : -- pull_requests: +3954 ___ Python tracker ___ ___ Python-bugs-list

[issue29762] Use "raise from None"

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue29762] Use "raise from None"

Serhiy Storchaka added the comment: New changeset 5affd23e6f42125998724787025080a24839266e by Serhiy Storchaka in branch 'master': bpo-29762: More use "raise from None". (#569) https://github.com/python/cpython/commit/5affd23e6f42125998724787025080a24839266e --

[issue29762] Use "raise from None"

Serhiy Storchaka added the comment: I don't think this is needed. The traceback points to the actual line -- the line with the "raise" statement. -- ___ Python tracker

[issue29762] Use "raise from None"

Josh Rosenberg added the comment: Particularly when the type of the exception isn't being changed, it's only altering the message to provide more information? -- ___ Python tracker

[issue29762] Use "raise from None"

Josh Rosenberg added the comment: To tie the exceptions to the actual line, would it perhaps make sense to copy over the traceback of the original exception using .with_traceback? -- nosy: +josh.r ___ Python tracker

[issue29762] Use "raise from None"

Changes by Serhiy Storchaka : -- pull_requests: +465 ___ Python tracker ___ ___

[issue29762] Use "raise from None"

New submission from Serhiy Storchaka: Sometimes after catching some exception the new exception of more appropriate type and with more appropriate message is raised. The initial exception often is not relevant to the final exception, it is raised only due to using EAFP rather than LBYL. It