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 Dennis Sweeney
Recipients Dennis Sweeney, Rotem Yaari, Yury.Selivanov, georg.brandl, larry, larsonreever, ncoghlan, oconnor663, python-dev, serhiy.storchaka, terry.reedy, vstinner, yselivanov
Date 2020-05-30.20:33:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1590870789.36.0.273644226224.issue25782@roundup.psfhosted.org>
In-reply-to
Content
For clarification, the existing behavior on master:
    When trying to raise the exception H,
        F -> G -> H -> I -> NULL
    becomes
        H -> F -> G -> NULL

    But when trying to set the exception A on top of
        B -> C -> D -> E -> C -> ...,
        it gets stuck in an infinite loop from the existing cycle.

My PR 20539 keeps the first behavior and resolves the infinite loop by making it
    A -> B -> C -> D -> E -> NULL,
    which seems consistent with the existing behavior.

So it should be strictly a bugfix. It also only changes the PyErr_SetObject code and not the PyException_SetContext code.
History
Date User Action Args
2020-05-30 20:33:09Dennis Sweeneysetrecipients: + Dennis Sweeney, georg.brandl, terry.reedy, ncoghlan, vstinner, larry, Yury.Selivanov, python-dev, serhiy.storchaka, yselivanov, oconnor663, Rotem Yaari, larsonreever
2020-05-30 20:33:09Dennis Sweeneysetmessageid: <1590870789.36.0.273644226224.issue25782@roundup.psfhosted.org>
2020-05-30 20:33:09Dennis Sweeneylinkissue25782 messages
2020-05-30 20:33:09Dennis Sweeneycreate