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 rhettinger
Recipients cool-RR, rhettinger
Date 2020-02-21.20:28:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582316929.71.0.79543808677.issue39717@roundup.psfhosted.org>
In-reply-to
Content
If this were new code, there would be a better case for the direct-cause style even though it is more cluttered and a bit slower.

I'm only questioning whether it make sense to change it in already deployed code, possibly risking breakage.  AFAICT, nothing is currently broken and the minor change in traceback wording would not confer a real benefit.
History
Date User Action Args
2020-02-21 20:28:49rhettingersetrecipients: + rhettinger, cool-RR
2020-02-21 20:28:49rhettingersetmessageid: <1582316929.71.0.79543808677.issue39717@roundup.psfhosted.org>
2020-02-21 20:28:49rhettingerlinkissue39717 messages
2020-02-21 20:28:49rhettingercreate