Fix test_ast_expr for Python 3.13 - #166
Open
thunze wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
13 tasks
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
1 participant
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 3.13 introduced the show_empty keyword argument to ast.dump. If show_empty is False, ast.dump omits empty lists and fields that are None from its output.
Since show_empty=False is the default in Python 3.13 and ast.dump previously behaved like show_empty=True, the test_ast_expr test currently fails for Python ≥3.13.
Assuming devtools wants to keep the default behavior of ast.dump, I've split the test_ast_expr test into two parts, one testing for the default behavior under Python <3.13, one testing for the default behavior under Python ≥3.13.
See also: https://hydra.nixos.org/build/294880588/nixlog/2/tail