Separate venv for Jupyter frontend #36766
Draft
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
|
Documentation preview for this PR (built with commit 3e38d13; changes) is ready! 🎉 |
added 2 commits
February 12, 2024 23:20
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.
📝 Checklist
from #36129 (comment)
Also splitting out the list of Jupyter frontend packages in the documentation: https://deploy-preview-36766--sagemath-tobias.netlify.app/html/en/reference/spkg/#standard-packages-jupyter-frontend
Part of:
⌛ Dependencies
build/bin/sage-spkg: Add options for checking, cleaning separately from build/install #36738, Normal Python packages: postpone wheel installation to the post-install phase #36743 (fixes for installing into JUPYTER_VENV should be based on there)