-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add symtable.py from 3.13.5
#6048
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
c87884a
Add `symtable.py` from 3.13.5
ShaharNaveh 32d63cc
Update symtable methods
ShaharNaveh 09a7fcf
Mark failing tests
ShaharNaveh cabfd73
Merge remote-tracking branch 'upstream/main' into update-symtable
ShaharNaveh 796b335
Apply review suggestions
ShaharNaveh 570fb54
Merge remote-tracking branch 'upstream/main' into update-symtable
ShaharNaveh 16f7737
Correct `symbols` attr
ShaharNaveh 433081b
Merge remote-tracking branch 'upstream/main' into update-symtable
ShaharNaveh 75981e3
Readd `nested` attrs
ShaharNaveh e66d264
Correct `type` return type
ShaharNaveh 8066fe5
Merge remote-tracking branch 'upstream/main' into update-symtable
ShaharNaveh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Correct
type return type
- Loading branch information
commit e66d264492c270f0d4255681f79b43e0769908d2
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Verify integer constant mapping for type property.
The
typ()method now returns integer constants instead of strings, which is a significant interface change. The mapping looks reasonable, but the fallback to-1for unhandled cases may not align with CPython's behavior.🏁 Script executed:
Length of output: 297
Ensure
typeproperty matches CPython’s string-based APICPython’s SymbolTable.get_type() returns strings like
"module"and"function", not integer codes. Our Rusttyp()currently returns integer constants and falls back to-1for any unhandled cases, which:Please update the implementation to either:
-1fallback with a dedicatedTYPE_UNKNOWNconstant—and add mappings for all types in CPython’s C implementation.Points to address:
// TODOand implement mappings for missing CPython types (generator, lambda, comprehension, etc.)-1fallback or replace it with a well-defined default constant🤖 Prompt for AI Agents