simonw / datasette · Architecture

The analyzed inventory holds 333 files: datasette 135, tests 102, docs 50, demos 7, .github 17, and 22 at the repository root. The analyzer classifies the top-level directories datasette, docs, and tests as likely subsystems. The primary language is Python, and repository topics include asgi, sqlite, json, csv, and docker. Inside the datasette package, datasette/app.py, datasette/cli.py, and datasette/__main__.py are flagged as likely entrypoints. Role records reference the subdirectories datasette/views, datasette/utils, and datasette/static, so view, utility, and static-asset code appears to live there.

Three files contain __main__ execution guards: datasette/__main__.py calls cli(), tests/fixtures.py calls cli(), and tests/build_small_spatialite_db.py calls generate_it to create spatialite.db. Two further entry candidates, datasette/app.py and datasette/cli.py, are flagged by filename heuristic rather than an execution guard. The reconstruction counts 5 entrypoints, 4,537 resolved static call relations, and 41 bounded execution paths, of which this packet itemizes 10. Of the 10 listed execution paths, exactly one stays inside the repository: datasette/__main__.py [__main__] calls datasette/cli.py [cli], terminating because cli is a leaf. None of the 10 listed execution paths is truncated, and none contains a cycle. The other nine listed paths all start at datasette/app.py and each ends after one step at an unresolved external boundary: Path, logging.getLogger, contextvars.ContextVar, collections.namedtuple, or Setting (the last five times).

Role labels in this section are the analyzer's inference from static resolved call degree and entrypoint membership, not runtime observations; paired numbers are incoming/outgoing static call counts. Ranked by incoming calls, the leading role records are datasette/static/edit-tools.js (808/808), datasette/utils/__init__.py (519/53), datasette/utils/asgi.py (369/21), datasette/app.py (356/197), and datasette/__init__.py (348/0). Two records carry the entry/orchestration label: datasette/app.py and tests/fixtures.py (87 in / 23 out). Four records are leaf/data-boundary candidates with zero outgoing calls: datasette/__init__.py (348 in), datasette/resources.py (227 in), datasette/permissions.py (114 in), and datasette/plugins.py (108 in). Six records cover datasette/views modules — table.py (46/283), query_helpers.py (126/82), database.py (12/153), table_create_alter.py (42/94), special.py (28/82), stored_queries.py (11/99) — all service/core candidates. Three test modules hold service/core role records: tests/test_api_write.py (123/158), tests/test_queries.py (18/114), and tests/test_plugins.py (20/108). Other service/core candidates include datasette/static/table.js (83/83) and datasette/utils/sqlite.py (109/30).

Every app.py-rooted listed path stops at a module-level external target rather than repository code: Path, logging.getLogger, contextvars.ContextVar, collections.namedtuple, or one of five Setting references. By resolution status, 15,850 of 21,338 static relations are external or unresolved and 5,488 are local. Dynamic dispatch, reflection, dynamic imports, runtime dependency injection, monkey-patching, generated code, and framework wiring are not resolved, so calls through them act as boundaries. Relation extraction is capped at 2,500 relations per file and 150,000 per repository, so large files can under-report their edges.

The analyzer recorded 21,338 static relations: 19,775 calls and 1,563 imports, split into 5,488 local and 15,850 external or unresolved. The packet's six dependency records come from package.json: runtime @codemirror/lang-sql ^6.3.3, codemirror ^6.0.1, rollup ^3.30.0, @rollup/plugin-node-resolve ^15.0.1, and @rollup/plugin-terser ^0.1.0, plus dev prettier ^3.0.0. Dependency parsing covers requirements-style manifests only; pyproject.toml dependency tables are not parsed, so the Python dependency set is not established. With 15,850 relations external or unresolved, this packet does not establish a complete module-to-module dependency map for the Python package.

Runtime wiring, reflection, dynamic imports, monkey-patching, generated code, framework runtime wiring, and dynamic dispatch are not resolved, so runtime connections between components are not shown. Install, run, and build inference is partial and installation commands are not verified; this asset therefore states no install or run commands. Bounded analysis inventories but does not parse files over 400 kB, minified bundles, and vendored directories, and relation extraction stops at 2,500 per file and 150,000 per repository. The packet names two skipped files, datasette/static/cm-editor-6.0.1.bundle.js and datasette/static/sql-formatter-2.3.3.min.js; their contents are not established. README-derived text is author_claimed at best and line-based extraction may capture code lines, so no README text is used as evidence in this asset. The inventory counts 102 test-like files, but what behavior they enforce at runtime is not established by this static packet.

Start with package.json and pyproject.toml, the packet's two manifest files, plus README.md; all three are classified as project-level important files. Continue with datasette/cli.py and datasette/app.py, both flagged as likely entrypoints, then datasette/__main__.py, whose guard roots the one listed in-repository path. Finish at the unresolved boundary targets — for example the Setting and logging.getLogger stops on the app.py paths — before changing code.