NotificationsYou must be signed in to change notification settings
Fork34k
Star71.2k

[3.13] gh-106287: Do not write objects after an unmarshalling error (GH-132715)#143833

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

serhiy-storchaka merged 1 commit intopython:3.13frommiss-islington:backport-ce8f5f9-3.13

Jan 14, 2026

Merged

[3.13] gh-106287: Do not write objects after an unmarshalling error (GH-132715)#143833

serhiy-storchaka merged 1 commit intopython:3.13frommiss-islington:backport-ce8f5f9-3.13

Jan 14, 2026

Conversation

Copy link

Contributor

miss-islington commentedJan 14, 2026•
edited by bedevere-appbot
Loading

Writing out an object may involve a slot lookup, which is not safe to do with
an exception raised. In debug mode an assertion failure will occur if this
happens.
(cherry picked from commitce8f5f9)

Co-authored-by: Duane Griffinduaneg@dghda.com

Issue:Assertion failure when marshalling buffer object with exception being set #106287

pythongh-106287: Do not write objects after an unmarshalling error (p…

707a499

…ythonGH-132715)Writing out an object may involve a slot lookup, which is not safe to do withan exception raised. In debug mode an assertion failure will occur if thishappens.(cherry picked from commitce8f5f9)Co-authored-by: Duane Griffin <duaneg@dghda.com>