Repository navigation
Conversation
When adapting via a non-SpecificationBase declaration (e.g. security proxy path), PyObject_IsTrue can return -1. That value was treated as truthy, returning the object with a pending exception still set. Fixes #361
Author
|
Closing for now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
In
IB__adapt__, the security-proxy fallback path storesPyObject_IsTrue(r)inimplementsand then testsif (implements). A-1error result is truthy in C, so the adapted object was returned with a pending exception still set.Check
implements < 0and returnNULL, matching thePyDict_Containserror handling on the fast path.Fixes #361
Test plan
__bool__); relying on the C API contract check