BUG,TYP: Allow subscripting iinfo and finfo generic types at runtime, or omit the type params
#27346
Conversation
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.
This fixes #27341 in two ways:
__class_getitem__classmethods tonumpy.(f|i)info, so that, at runtime,np.info[Any]won't raise aTypeErroranymore.typing.TypeVartype-parameters ofnumpy.(f|i)info. Type checkers will now effectively interpret a "bare"iinfoasiinfo[integer[NBitBase]], andfinfoasfinfo[floating[NBitBase]]. See TYP: Assume thattyping_extensionsis always available in the stubs #27132 for an explanation on how this is possible on Python <3.12.