Document preserved shebangs about marimo HOT 5 OPEN

could it be header_comment or just header in the markdown? since it would be nice to preserve these comments and since both script and nix are slightly different in their comment structuer

from marimo.

That would be nice because there might be other header comments that could be leveraged.
Arguments for having sections:

• Most / single hashbangs aren't useful since .md files aren't runnable
• writing the env becomes more cumbersome and prone to error
• In the header form (even with # stripped out), the block would still have to be parsed to be usable and require sandbox / nix particular logic for the consumer

from marimo.

the block would still have to be parsed to be usable and require sandbox / nix particular logic for the consumer

Why does it? Why can't we just not touch the header and leave it as is? I don't think marimo can/should be opinionated on how to construct the env, especially since there isn't one way.

from marimo.

I think there should be parity with the python format. So even if there isn't a nix section, maybe there should be a sandbox section that extracts the relevant # /// script section. Even though there's not one way to bootstrap an env, the marimo seems to be embracing the PEP specification

from marimo.

Could we not go a level higher, and instead of preserving # /// script, we just preserve the whole comment as-in without any modification?

---
title: Notebook
marimo-version: 0.0.0
width: medium
comment: |
    #! /usr/bin/env nix
    #! nix shell --impure --expr ``
    #! nix with (import (builtins.getFlake ''nixpkgs'') {});
    #! nix    python311.withPackages (
    #! nix            ps: with ps; [ marimo uv setuptools ]
    #! nix    )
    #! nix ``
    #! nix --command marimo edit --sandbox
    # /// script
    # requires-python = ">=3.11"
    # dependencies = [
    #     "numpy",
    # ]
    # ///
---   

from marimo.