Skip to content

ENH: standalone execution check of built notebooks #2

Description

@mmcky

A lecture can build cleanly and still break for a reader who downloads it. Benefit: match running a lecture standalone.

The gap is the artifact, not kernel isolation — jupyter-cache already isolates kernels per notebook (single_nb_execution). Download/Colab notebooks come from sphinx-tojupyter (containers/quantecon-build/environment.yml:67) via the jupyter builder (build-lectures/action.yml:104, output :126, staged to _build/html/_notebooks :71-76), and nothing here executes them, so conversion defects ship silently. Scope is executing them (PLAN.md:117); both options first floated are dated — a venv off a base anaconda image fights the pinned-as-a-set policy (PLAN.md:96-102), and the preferred jupyter-book/MyST-NB/myst-parser engine runners were never pursued upstream.

Work items

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementImprovement to existing content or functionalitylow-priorityNice to have, no time pressure

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions