Open
Conversation
This was referenced Apr 12, 2026
Add jedi_resolver.py that enriches the call graph after build by using Jedi's static analysis to resolve Python method calls that tree-sitter alone cannot determine (e.g. factory return types, dynamic dispatch). - Lazy-imports jedi (optional dependency via [enrichment] extra) - Pre-filters call targets to skip stdlib, reducing runtime from ~36s to ~3s - Adds CALLS edges for resolved method calls with jedi_resolved=true marker - Integrates as a post-build step, not a parser dependency
c73a414 to
0028905
Compare
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
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
jedi_resolver.pyfor post-build Python method call resolution using Jedi static analysis[enrichment]extraSplit from #158 (2/5). Independent -- targets main.
Test plan
🤖 Generated with Claude Code