module Noir::ImportGraph::Python

Overview

---

Python flavour.

Python imports are dotted-module paths anchored at one of:

1. app_base_path — the project's source root (the app directory passed by the analyzer).
2. The current file's directory, for relative imports (from . import x, from .. import x).

The resolver walks the dotted path one segment at a time, preferring directories (Python packages) over file siblings (modules) until either a leaf .py is found or the path runs out — matching the behaviour expected by the existing Django / FastAPI / Tornado analyzers.

Lives under the shared Noir::ImportGraph umbrella so a future Python analyzer migration off the legacy PythonParser (still used by Flask) can reuse the same resolver. Until that migration lands the JVM / JS / Python flavours all share the top-level module but each operates on its own data shapes — Python's hashes look different from the JVM ImportRef form because Python returns import-name → file-path mappings rather than a yield of files.

Defined in:

miniparsers/import_graph.cr

Class Method Summary

• .find_imported_modules(app_base_path : String, file_path : String, content : String | Nil = nil) : Hash(String, Tuple(String, Int32))

  Find every import and from … import … line in content and resolve each name to a {filepath, package_type} tuple.

• .find_imported_package(package_path : String, dotted_as_names : String) : Array(Tuple(String, String, Int32))

  Resolve a dotted Python identifier (a.b.c or a.b.c, d.e as f) under package_path.

Class Method Detail