TryExamples directive: fix missing kernels in CircleCI deployments - #182
Merged
Conversation
Co-Authored-By: Loïc Estève <1680079+lesteve@users.noreply.github.com>
Collaborator
|
let's try. |
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
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.
Description
This PR updates the URL used to access the notebooks generated by the
TryExamplesdirective, similar to sphinx-gallery/sphinx-gallery#1336. This enables viewing and interacting with the examples on Sphinx-based documentation websites.As originally mentioned in the above issue, here is a related discussion. Adding
index.htmlto the URL somehow makes the notebooks/examples display as intended when the "Try it" or the "Open in tab" buttons are clicked.Additional context
This came up in numpy/numpy#26745 where I am trying to integrate
jupyterlite-sphinxfor the NumPy v2 documentation website, which uses CircleCI artifacts for documentation builds on PRs.P.S. Thanks to @lesteve for the pointer!