Cant generate dependencies

[Gutieala1]

Stacklit has a problem with handling python imports, I had to build a script to use pythons AST parser alongside stacklit

[atharvasingh7007]

I’m taking a look at this and planning a narrow fix for Python import resolution when building dependency edges.

[thegdsks]

Fixed in #8.

The graph builder's import resolver only understood path-style relative imports (./foo, ../foo), which is how JS and Go work. Python's dot notation (.models, ..utils, myapp.db.client) fell through and got treated as external/unresolvable.

The fix converts dot-prefix imports to path equivalents before matching, and slash-converts dotted absolute imports so they line up with module names stacklit already knows about. Tested against a multi-package Python project, edges come through correctly now.

If you had a script doing AST parsing alongside stacklit you shouldn't need it anymore. This handles import X, from .X import Y, and from ..X.Y import Z natively.