Introduce a setup cell #1075
Merged
Introduce a setup cell #1075
Conversation
This file contains 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
ResolvedSince we show the source until evaluated, it looks a bit confusing when opening notebooks with no setup:
I'd be fine with always collapsing it when the source is empty. This would mean that newly created notebooks have it collapsed too (which I actually prefer), or we could make this cell in insert mode right away for notebooks. @josevalim let me know what you think :) |
|
What if the text says: "Install dependencies and setup notebook"? |
josevalim
approved these changes
Mar 28, 2022
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.
The first towards improved dependency management. This introduces a special cell for code that initializes the notebook (in practice it's just a code cell, but it has a slightly different UI).
setup_cell.mp4
The cell is automatically shown in all notebooks, but it's persisted only if it has an actual content. In a way, we just introduce a convention on where to install dependencies and set global configuration.
As shown above, reevaluating the cell automatically restarts the runtime (as indicated by the run button), which makes adding a new dependency more intuitive (as opposed to the error + restart runtime button we currently have).
The setup source is always shown when creating/opening a notebook (so that the user can always review the code), and it gets collapsed once run (since it is a form of boilerplate, conceptually run only once).