Skip to content

Conversation

@vstinner
Copy link
Member

@vstinner vstinner commented Jun 17, 2019

Mention explicitly that PyObject_CallXXX() functions raise an
exception an failure.

https://bugs.python.org/issue37194

Mention explicitly that PyObject_CallXXX() functions raise an
exception an failure.
@miss-islington
Copy link
Contributor

Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8.
🐍🍒⛏🤖

@miss-islington
Copy link
Contributor

Sorry, @vstinner, I could not cleanly backport this to 3.8 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 1ce2656f13e726b3b99d4c968926908cff1f460a 3.8

@bedevere-bot
Copy link

GH-14157 is a backport of this pull request to the 3.8 branch.

vstinner added a commit that referenced this pull request Jun 17, 2019
Mention explicitly that PyObject_CallXXX() functions raise an
exception an failure.

(cherry picked from commit 1ce2656)
vstinner added a commit that referenced this pull request Jun 17, 2019
Mention explicitly that PyObject_CallXXX() functions raise an
exception an failure.

(cherry picked from commit 1ce2656)
lisroach pushed a commit to lisroach/cpython that referenced this pull request Sep 10, 2019
Mention explicitly that PyObject_CallXXX() functions raise an
exception an failure.
DinoV pushed a commit to DinoV/cpython that referenced this pull request Jan 14, 2020
Mention explicitly that PyObject_CallXXX() functions raise an
exception an failure.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation in the Doc dir skip news

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants