Add LP_SAFEARRAY.from_param to hints.pyi.
#687
Merged
Conversation
This file contains 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.
While reviewing
test_safearray, I noticed that the type checker raises an error because it infers the type of a variable assigned an instance generated byLP_SAFEARRAY.from_paramasLP_SAFEARRAY | _CArgObject.This behavior stems from the
from_paramclassmethod intypeshed'sctypesmodule, which returnsSelf | _CArgObjectas defined here.At runtime, since
POINTER(sa_type)overridesfrom_param,Selfis consistently returned.To suppress this false positive, I will define and override
LP_SAFEARRAY.from_paraminhints.pyi.