DOC-5831 Tool to convert TCE examples to notebooks #2273
+3,706
−0
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
cmilesb
approved these changes
Oct 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've used Augment to make the
jupyterizetool using the spec-driven approach outlined here again. The tool has been through several iterations and seems to be fairly useful/reliable for the few simple cases I've tried, but it will probably require some real-world usage before it can be used in a fully automated tool chain to update notebooks from doc examples (and maybe we want to rewrite it in Rust or something for production usage?)There's a quickstart guide and a longer README in the
build/jupyterizefolder. The spec is intended for AI use and is probably too long and boring for a human reader to bother with. All feedback welcome :-)