docs: add papermill-tenki as a real-world remote-execution engine example - #903
Open
darolpz-luxor wants to merge 4 commits into
Open
docs: add papermill-tenki as a real-world remote-execution engine example#903darolpz-luxor wants to merge 4 commits into
darolpz-luxor wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a short "real-world engine" subsection to
docs/extending-entry-points.rst,pointing readers to papermill-tenki
as an example of an engine that executes notebooks on remote infrastructure
(disposable Tenki Sandbox microVMs), discovered through the same
papermill.engineentry point the surrounding docs already describe.The existing example engine is intentionally minimal (it just times cells). This
gives readers a concrete, installable example of a non-trivial engine — one that
runs notebooks off-machine and returns the executed notebook with outputs.
Docs-only change; no code or behavior changes. The example notes it requires a
Tenki account and
TENKI_API_KEY, linking to the package README for setup.No associated issue (docs enhancement).