Textualize / rich · Source walkthrough

This asset guides your reading through ordered stops: orientation, an execution trace, library core code, and change-sensitive blocks. Every line range refers directly to analyzed files in revision 9d8f9a372cc5916fd4781fec207ced7ddac2f08f. In this walkthrough, a block is the analyzer's line-addressable semantic unit, and every block description represents the analyzer's static inference rather than a runtime execution trace.

Start with top-level landmarks and example scripts to get oriented before inspecting library implementations:

• setup.py:1-8: module setup.py. The analyzer notes this file-level block represents the analyzed source file setup.py and provides its file-level container.
• examples/attrs.py:1-53: module examples/attrs.py. The analyzer identifies this block as the file-level container for examples/attrs.py.
• examples/cp_progress.py:1-19: module examples/cp_progress.py. The analyzer records this block as the file-level container for examples/cp_progress.py.
• examples/downloader.py:1-81: module examples/downloader.py. The analyzer records this block as the file-level container for examples/downloader.py.
• examples/print_calendar.py:1-70: module examples/print_calendar.py. The analyzer records this block as the file-level container for examples/print_calendar.py.
• examples/suppress.py:1-23: module examples/suppress.py. The analyzer records this block as the file-level container for examples/suppress.py.

The analyzer reconstructs an execution story grounded around an example script, tracing direct invocation paths into local classes and external calls:

• examples/attrs.py:31-53: main_guard __main__. The analyzer notes this block gates code that should run when examples/attrs.py is executed directly.
• examples/attrs.py:1-53: module examples/attrs.py. The analyzer records this block as the file-level container for examples/attrs.py.
• examples/attrs.py:26-28: class Model. The analyzer infers that Model groups related behavior under one class boundary.

None of the 8 blocks in the analyzer's core-code lesson lie in library code.

• Non-library blocks in that lesson include examples/attrs.py:31-53 (main_guard __main__), examples/attrs.py:26-28 (class Model), and benchmark blocks in benchmarks/benchmarks.py: benchmarks/benchmarks.py:14-61 (class TextSuite), benchmarks/benchmarks.py:15-20 (function TextSuite.setup), benchmarks/benchmarks.py:22-23 (function TextSuite.time_wrapping), benchmarks/benchmarks.py:25-26 (function TextSuite.time_indent_guides), benchmarks/benchmarks.py:28-29 (function TextSuite.time_fit), and benchmarks/benchmarks.py:31-32 (function TextSuite.time_split).

The library reading set is selected deterministically by the AI Frontier lab based on static call degree, not from an analyzer lesson. The modules and their prominent blocks include:

Module rich/text.py is inferred as an entry/orchestration candidate with 707 incoming and 44 outgoing calls:

• rich/text.py:118-1335: class Text. The analyzer notes this class block groups related behavior under one class boundary.
• rich/text.py:1106-1183: function Text.divide. The analyzer notes Text.divide encapsulates an operation and connects to 13 downstream call or import relations.

Module rich/style.py is inferred as a service/core candidate with 474 incoming and 26 outgoing calls:

• rich/style.py:40-759: class Style. The analyzer notes this class block groups related behavior under one class boundary.
• rich/style.py:131-205: function Style.__init__. The analyzer notes Style.__init__ encapsulates an operation and connects to 7 downstream call or import relations.

Module rich/console.py is inferred as an entry/orchestration candidate with 416 incoming and 78 outgoing calls:

• rich/console.py:581-2642: class Console. The analyzer notes this class block groups related behavior under one class boundary.
• rich/console.py:2352-2604: function Console.export_svg. The analyzer notes Console.export_svg encapsulates an operation and connects to 37 downstream call or import relations.

Module rich/segment.py is inferred as an entry/orchestration candidate with 337 incoming and 7 outgoing calls:

• rich/segment.py:61-696: class Segment. The analyzer notes this class block groups related behavior under one class boundary.
• rich/segment.py:630-696: function Segment.divide. The analyzer notes Segment.divide encapsulates an operation and connects to 16 downstream call or import relations.

The change-guide lesson highlights library blocks where the static graph demonstrates stronger coupling:

• rich/console.py:581-2642: class Console. The analyzer suggests Console groups related behavior under one class boundary.
• rich/style.py:40-759: class Style. The analyzer suggests Style groups related behavior under one class boundary.
• rich/text.py:47-115: class Span. The analyzer suggests Span groups related behavior under one class boundary.
• rich/text.py:118-1335: class Text. The analyzer suggests Text groups related behavior under one class boundary.
• rich/segment.py:61-696: class Segment. The analyzer suggests Segment groups related behavior under one class boundary.
• rich/style.py:498-561: function Style.parse. The analyzer notes Style.parse encapsulates an operation and connects to 17 downstream call or import relations.

This walkthrough reflects bounded static analysis only. Dynamic dispatch, reflection, monkey-patching, runtime dependency injection, dynamic imports, and framework runtime wiring remain unresolved. Install, run, and build inferences are partial, and installation commands are not verified. In addition, 6,703 static relations remain external or unresolved in the analyzed dataset, and block annotations represent static inferences carrying confidence scores.