Update builds
signature inspection for python 3.11.4 change
#497
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.
python/cpython#105080 updates the behavior of
inspect.signature
to walk through a class' mro in search of its signature, rather than just defer to the most recent definition of__new__
.This PR updates the signature inspection logic of
builds
to match this new behavior ofinspect.signature
across all versions of Python. I.e. this effectively serves as a backport.Here is an example that exhibits this change in behavior:
Before:
The signature of
A.__new__
was preferred over that ofB.__init__
even though the latter is closer toC
in the inheritance hierarchy.After:
C's signature is that of
B.__init__