Textualize / rich

This repository is the source of a Python distribution named rich: in setup.py, a __main__ guard calls setuptools.setup(name="rich").

• The GitHub description presents the project as a Python library for rich text and formatting in the terminal, and the listed homepage is https://rich.readthedocs.io/en/latest/.
• It is written almost entirely in Python (1,701,402 language bytes versus small Batchfile and Makefile shares), with GitHub topics including terminal, tables, markdown, syntax-highlighting, progress-bar, emoji, traceback and tui.
• License metadata says MIT, and a LICENSE file is present.
• Metadata records a v15.0.0 release published 2026-04-12 and 57,362 stars as of 2026-09-14.
• The analyzer inventoried 553 files and 3 build/dependency manifests; its summary describes the project as organized around assets, benchmarks, docs and examples, and flags rich/ (with tests/, benchmarks/ and docs/) as a subsystem.

• setup.py's __main__ guard calls setuptools.setup(name="rich"); it is the packaging entry point.
• The analyzer's repository summary states that no clear executable starting point was established for the project.
• It detected 63 entrypoints and traced 612 bounded execution paths.
• examples/attrs.py constructs Point3D, Triangle and Model objects under a __main__ guard.
• Bounded traces from that guard reach Model and Triangle locally and terminate at unresolved external boundaries such as print, SystemExit and attr.Factory.
• examples/cp_progress.py takes exactly three argv entries and copies file argv[1] to argv[2] through progress.open; examples/downloader.py passes its arguments to a download() call; examples/print_calendar.py parses a year with argparse and calls print_calendar.
• Many rich/*.py modules carry __main__ demo blocks, often marked # pragma: no cover (for example rich/console.py, rich/markdown.py, rich/syntax.py), which suggests the package serves as its own demonstration gallery.

• Four top-level directories are flagged as subsystems: rich/ (the importable package), tests/, benchmarks/ and docs/.
• The analyzer recorded 11,248 static relations — 9,630 calls and 1,618 imports — of which 4,545 resolve locally and 6,703 remain external or unresolved.
• By static incoming-call degree the most referenced modules are rich/text.py (707), rich/style.py (474), rich/console.py (416) and rich/segment.py (337); rich/console.py also has 78 outgoing calls, and the analyzer labels these core/orchestration candidates.
• Test modules invert that shape: tests/test_text.py makes 329 outgoing calls with none incoming, tests/test_highlighter.py 231 and tests/test_segment.py 221 — tests drive library code rather than the reverse.
• rich/pretty.py (149 incoming) and rich/progress.py (133) are also heavily referenced, while rich/default_styles.py has 1 incoming against 154 outgoing calls, consistent with a provider of default styles.

• The dependency records in the packet come from one manifest, docs/requirements.txt: alabaster 1.0.0, Sphinx 8.2.3, sphinx-rtd-theme 3.0.2 and sphinx-copybutton 0.5.2, all pinned.
• This picture is partial: the analyzer parses only requirements-style manifests and does not read pyproject.toml dependency tables, although the repository holds 3 build/dependency manifests.
• The test suite spans 68 test files, including tests/conftest.py.
• Visible test functions cover text operations (test_span, test_add, test_eq in tests/test_text.py), segment handling (test_split_lines, test_simplify in tests/test_segment.py) and highlighting (test_highlight_regex, test_highlight_json_with_indent in tests/test_highlighter.py).
• Several test files also carry __main__ blocks that render fixtures and print results, e.g. tests/test_table.py and tests/test_card.py.
• Install, run and build inference is partial and installation commands are unverified, so this packet yields no runnable setup instructions.

• Start with README.md and pyproject.toml; the analyzer classifies both as project-level important files.
• Then skim setup.py for packaging details and LICENSE for terms.
• For code, read the highest-degree modules in this order: rich/text.py (its Text class spans lines 118–1335), then rich/style.py, rich/console.py and rich/segment.py.
• Finish with the runnable examples flagged as likely entrypoints: examples/attrs.py, examples/cp_progress.py, examples/downloader.py and examples/print_calendar.py.
• A compact end-to-end sample is rich/pager.py's demo block, which imports make_test_card from rich/__main__.py and displays it through console.pager.

• 6,703 of the 11,248 static relations remain external or unresolved, so many cross-file call targets were not bound to definitions.
• Reflection, runtime dependency injection, dynamic imports, monkey-patching, generated code, framework runtime wiring and dynamic dispatch are not resolved by this static analysis.
• Nothing here establishes runtime behavior: install, run and build inference is partial and unverified, and the bounded scan does not parse files over 400 kB, minified bundles or vendored directories, with relation extraction capped per file and per repository.
• README text is extracted line by line and may capture code lines, so any README-derived statement should be treated as an author claim.
• One execution path contains a detected static call cycle; whether that reflects a real runtime cycle is not established.
• The 612 bounded execution paths are static analyzer constructions; no code was executed for this asset.

• rich/text.py: Span (lines 47–115) and the large Text class (118–1335); rich/segment.py: Segment (61–696) plus Segments and SegmentLines; rich/style.py: Style (40–759) and StyleStack.
• rich/console.py: ConsoleOptions (113–243), Capture (310–340), PagerContext (364–400) and ScreenContext (403–447).
• rich/progress.py: track(), wrap_file(), ProgressColumn and the column classes SpinnerColumn, TextColumn and RenderableColumn; rich/pretty.py: install() and the Pretty class.