BUG: Fix an issue wherein importing numpy.typing
could raise
#19533
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.
closes #19521
Backport of #19525 in addition to two fixes for the to-be closed issue.
On a semi-frequent we're running into issues with numpy.typing when the following 2 conditions are met:
Ideally we'd just run a CI job without typing-extensions installed and see if the tests run as expected
but unfortunately this is not possible, as it is an (indirect) hard dependency of pytest.
This PR instead opts for an alternative approach: the test introduced herein reloads the numpy.typing
submodules after manually invalidating typing-extensions, thus making the package inaccessible as if it
weren't installed in the first place.