Standard Python/pytest/unittest test-file conventions. A file under any of these patterns ships with python -m pytest or python -m unittest and never serves real traffic in production. Centralized so every analyzer can opt in via next if PythonEngine.python_test_path?(path).

• /tests/ — pytest discovery default (Django, Litestar, FastAPI all use it)
• tests.py — the legacy Django per-app test module
• test_*.py — unittest / pytest default discovery
• *_test.py — pytest-go style suffix (rare in Python, but cheap to include)

Build 1-hop callees observed in body (a handler's Python source). body_start_line is the 0-based file line at which body's first character sits, so tree-sitter rows can be translated into absolute call-site lines (1-indexed). Use when one body maps to multiple endpoints (e.g. Sanic's multi-method routes) so the tree-sitter parse happens once and the same Callee list gets pushed onto each endpoint.

Note: callers using parse_code_block(lines[def_idx..]) should pass def_idx because that helper keeps the def line. Callers using extract_function_body(lines, def_idx) should pass def_idx + 1 because that helper skips the def line. When definition_base_path is provided, callees with reachable same-file or imported Python definitions are rewritten to that definition location; unresolved callees keep their call-site path/line.

Walk forward from decorator_line past any stacked decorators, blank lines, and comments to the actual def / async def that they apply to. Returns the 0-based line of the def, or nil if none is found before a non-decorator/non-blank statement.

This exists because real-world Python decorator stacks (@app.post(...) + @auth_required, blank-line spacers, or a # comment between the route decorator and the def) make the "def is at decorator_line + 1" assumption silently wrong — both for parameter extraction and for handler-body parsing.

Resolve every import and from … import … in the file to {name => {filepath, package_type}}. Thin delegator over Noir::ImportGraph::Python.find_imported_modules so future Python analyzers (or new tagger logic) can call the resolver directly without going through PythonEngine.

See #find_imported_modules — same delegator.

Finds all parameters in JSON objects within a given code block

Given a 0-based index into lines whose content line is known to open a Python call whose ( is unbalanced, join continuation lines until the running paren delta drops to ≤ 0. Returns the joined string with newlines collapsed to single spaces so analyzer-side regexes don't need a multi-line flag. The caller is expected to short-circuit (return line) when the call already balances on the same line — this method always walks forward at least once.

Parses a function or class definition from a string or an array of strings

Parses the definition of a function from the source lines starting at a given index

Convenience wrapper around #build_callees_from: parse + push in one call when one body maps to exactly one endpoint. Endpoint#push_callee enforces dedup and the per-endpoint cap.

Net ( − ) count on a single Python source line, ignoring parens that fall inside single- or double-quoted strings on the same line. Sufficient for decorator / function-call headers, which never carry triple-quoted strings on the call line.

Used by analyzers that walk source line-by-line and need to join continuation lines into one logical call (e.g. multi-line decorators in FastAPI / Litestar / Sanic / Bottle, multi-line Route(...) entries in Starlette).

Returns the literal value from a string if it represents a number or a quoted string