Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-sol· openaiHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

Marimo's print routing breaks Numba compilation In notebooks that do not use mo.Thread,…

  1. User

    Marimo's print routing breaks Numba compilation

    In notebooks that do not use mo.Thread, print must retain builtin identity so Numba can compile functions that call it. mo.Thread must continue routing output to the spawning cell, with output isolation between concurrent threads.

    Interface

    No new interfaces are introduced.

  2. Assistant

    I’ll trace the print-routing implementation and its thread tests, then patch the narrowest layer that preserves builtin print outside mo.Thread while keeping thread-local routing.

  3. Assistant

    rg isn’t installed in this checkout, so I’m using the repository’s available search tools and continuing with the same scope.

  4. Assistant

    The root cause is confirmed: every kernel injects a Python wrapper into the notebook globals before any thread exists, so print is no longer the builtin that Numba recognizes. I’m moving that injection to the first mo.Thread construction and adding kernel-level regression coverage for identity and concurrent routing.

  5. Assistant

    The targeted runtime tests now pass. The lazy installation preserves builtin identity until mo.Thread() is actually used; once installed, routing remains per-thread because the wrapper still resolves each thread’s copied execution context and spawning cell ID. I’m doing the final type/diff checks now.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.