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.
List comprehensions no longer get their own scope [1], so adding a level to the (eventual) call to
sys._getframe
goes outside the actual caller. If running inpytest
(so that there is a scope outside the caller), you end up looking in some unrelated scope. If you are running a script, thensys._getframe
raises an error that the level is out of bounds.The
Bitwise operations
warning intest_scalar_unary
appears to always be raised, so remove the condition.[1] https://docs.python.org/3.12/whatsnew/3.12.html#whatsnew312-pep709
I'm not entirely sure why neither issue is seen on CI, but there are so many tests/workflows, I'm also not sure which one to check. I guess I'll see how this goes in this PR.
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.