镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Add guide on executable documentation #157

Open

Description

@danielballan

Following up #136, investigate whether we should recommend:

  • Jupytext
  • the ipython sphinx directive
  • the matplotlib plot directive

I suspect that Jupytext is now the best way to do this, and more compatible with a Markdown-based approach, but I want to educate myself more.

Activity

  1. danielballan commented on Feb 13, 2024

    @danielballan
    CollaboratorAuthor

    I started looking at this more today, aligned with a day-job task. I intend to put up a PR on this in the next week or so.

  2. danielballan commented on Nov 11, 2024

    @danielballan
    CollaboratorAuthor

    Following up here to mention, belatedly, that I have a self-contained demo repo illustrating some nice patterns for interactive documentation:

    • source in Markdown (not ipynb JSON)
    • auto-generated branch with ipynb JSON
    • published HTML with executed code
    • Binder
    • Jupyter Lite (proof of concept)

    https://github.com/danielballan/interactive-tutorial-demo

    I could imagine promoting this to live in the scientific-python org if there is support and interest.

  3. danielballan commented on Nov 11, 2024

    @danielballan
    CollaboratorAuthor

    Given the range of technologies and use cases, I think it would be too heavy to include in this repository, so I would advocate for linking out. Most major projects have a dedicated "examples" repo separate from the main library to do things like this.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions