Fix TypeError in is_literal_or_name on unhashable set literals#339
Merged
fsouza merged 1 commit intoPyCQA:mainfrom Feb 18, 2026
Merged
Conversation
ast.literal_eval raises TypeError (not just SyntaxError/ValueError) when evaluating set literals containing unhashable types like dicts or lists. Catch TypeError as well to prevent the crash. Fixes PyCQA#325 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
2 participants
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.
Summary
ast.literal_evalraisesTypeError(not justSyntaxError/ValueError) when evaluating set literals containing unhashable types like dicts or lists (e.g.,{{}},{[]})TypeErrorto the existing except clause to prevent the crashFixes #325
Test plan
is_literal_or_name("{{}}}")andis_literal_or_name("{[]}")(should return False, not crash)