Codex review on #167 (round 5). from models import User as Account then Account(): the Imports edge correctly targets User, but later CallsName/ReferencesType edges on the alias Account have no alias→target scope to connect them back to User, so they stay unresolved or bind to an unrelated local Account.
This needs a Python import-alias scope the resolver consults — analogous to the Rust per-module use-scope machinery (#61: import_scope_start/end_byte, import_mod_id columns + imports:: resolution). It's a resolver-side subsystem, not an extraction tweak, so it's out of scope for the #167 indexing PR.
Sibling of #172 (Implements resolution preference) — both are Python resolution refinements. The import TARGETS are already captured correctly (so the dependency on models.User is visible); what's missing is binding alias uses to it.
Codex review on #167 (round 5).
from models import User as AccountthenAccount(): the Imports edge correctly targetsUser, but laterCallsName/ReferencesTypeedges on the aliasAccounthave no alias→target scope to connect them back toUser, so they stay unresolved or bind to an unrelated localAccount.This needs a Python import-alias scope the resolver consults — analogous to the Rust per-module
use-scope machinery (#61:import_scope_start/end_byte,import_mod_idcolumns +imports::resolution). It's a resolver-side subsystem, not an extraction tweak, so it's out of scope for the #167 indexing PR.Sibling of #172 (Implements resolution preference) — both are Python resolution refinements. The import TARGETS are already captured correctly (so the dependency on
models.Useris visible); what's missing is binding alias uses to it.