ENH: add the JupyterLite browser runtime (JupyterLite split 3/4) - #14144
Draft
natinew77-creator wants to merge 2 commits into
Draft
ENH: add the JupyterLite browser runtime (JupyterLite split 3/4)#14144natinew77-creator wants to merge 2 commits into
natinew77-creator wants to merge 2 commits into
Conversation
The setup cell that installs MNE into the browser kernel and patches what Pyodide does not provide, plus the pyvista-js backend for MNE's 3D renderer that it appends. Wired up by the next PR in the series.
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.
Part 3 of the split of #13925. Parts 1 and 2 are #14128 and #14135.
Adds the browser side of the JupyterLite docs: the setup cell prepended to every notebook, and the vtk.js backend for MNE's 3D renderer that it appends. The setup cell installs MNE with piplite and patches what Pyodide does not provide, mainly HTTP data fetching and the readers that expect a file on disk. The renderer exists because VTK cannot load in WebAssembly, so only MNE's final drawing step is replaced and the transform maths stays with MNE.
Both are plain string constants with no imports beyond each other, so nothing in the build touches them yet. The Sphinx wiring that uses them is the last PR in the series.