Where to put new files:

• New files should go into a top-level subfolder, named after the article slug. For example: my-awesome-article

How to merge your changes:

1. Make sure the CI code style tests all pass (+ run the automatic code formatter if necessary).
2. Find an RP Team member on Slack and ask them to review & approve your PR.
3. Once the PR has one positive ("approved") review, GitHub lets you merge the PR.
4. 🎉

Code examples for the Python Sandbox: Run Untrusted Code in Docker and MicroVMs tutorial. Files live in the python-sandbox/ top-level folder, named after the article slug.

Generated from the tutorial markdown with the post-materials skill. The Python files and rootfs/sbin/run-job are byte-for-byte copies of the article's code blocks.

Notes:

• python-sandbox/ruff.toml extends the root pyproject.toml and sets quote-style = "preserve". Without it, ruff format --check would rewrite the PEP 701 nested same-quote f-string at the end of compare.py (f"...{result["exit_code"]}..." to result['exit_code']), which would diverge from the article.
• requirements.txt pins RestrictedPython==8.5, matching the post's dependencies field and the install command in the article.

🤖 Generated with Claude Code