A reactive notebook for Python — run reproducible experiments, query with SQL, execute as a script, deploy as an app, and version with git. Stored as pure Python. All in a modern, AI-native editor.
MW002: unsafe-system-call
🌐 WASM ❌ Not Fixable
MW002: System calls that fail in WASM/Pyodide.
What it does
Walks the AST of each cell looking for calls to functions like
os.system(), os.fork(), signal.signal(), multiprocessing.Pipe(),
and breakpoint() that have no meaningful implementation in WASM.
Why is this bad?
These functions depend on OS features (process spawning, signal
handling, debugger attachment, unsupported multiprocessing
synchronization, or IPC) that don't exist in a browser environment.
They will raise OSError, NotImplementedError, or hang silently.
Examples
Problematic:
import os
os.system("ls")
Problematic:
breakpoint()
Problematic:
import multiprocessing
multiprocessing.Pipe()
Solution: Remove or guard these calls behind a WASM detection check.