wrong import relationship in table edges #2409

Activity

1. maxmilian commented on Oct 8, 2026

   

   maxmilian

   on Oct 8, 2026

   Contributor

   More actions

   Reproduced on current main (b635dd4): for an absolute Python import, findPythonModuleFile in src/resolution/import-resolver.ts matches any project file whose path ends with the module path, so stdlib import logging binds to app/core/logging.py whenever such a file exists. This looks like exactly the case open PR #1921 addresses ("could bind import json to a project serializers/json.py"); it resolves absolute imports only from evidence-based package roots instead of a filename-suffix match. Linking so the two are tracked together.
2. colbymchenry commented on Oct 22, 2026

   

   colbymchenry

   on Oct 22, 2026

   Owner

   More actions

   Thanks for the report! This is fixed on main by #1921, which resolves Python imports from your project's own package roots the way Python finds modules, so import logging stays the standard library even when the project has an app/core/logging.py. We checked it with that layout: v1.6.2 linked import logging to app/core/logging.py (and logging.getLogger(...) to a same-named function in it), while current main links neither, after a fresh index or a sync. The fix is on main and ships in the next release after 1.6.2; re-index your project after upgrading.
3. colbymchenry

   closed this as completedon Oct 22, 2026