-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enforce a top-down order of execution #3229
Comments
If you did that, isn't it essentially just a console? |
You can take a look at nodebook - https://github.com/stitchfix/nodebook
…On 18-Jan-2018 2:03 AM, "Thomas Kluyver" ***@***.***> wrote:
If you did that, isn't it essentially just a console?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3229 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AImSDCd9OGTHy6OXcWR-zfIljFvcRcbUks5tLlk0gaJpZM4RhzS0>
.
|
Oh neat, I hadn't seen that before. :-) |
@Madhu94 that's awesome! Thanks! I'll give it a shot and see if its a good solution. This sentence: "This prevents messy and difficult to maintain out-of-order execution which frequently occurs in vanilla Jupyter notebooks where each cell modifies the global state." captures exactly the problem I was looking for a solution for. This also outlines the issue in more depth: https://multithreaded.stitchfix.com/blog/2017/07/26/nodebook/ |
Looks like I'm not the only one who has this concern: https://www.youtube.com/watch?v=7jiPeIFXb6U I'm re-opening as nodebook didn't really provide much of satisfactory solution and I think it would be better if supported natively by the notebook. |
Is it possible to force a top-down order for cell execution? New cells to execute would only be at the bottom of them notebook and existing cells would essentially be immutable. Maybe if a user wanted to edit or re-execute a cell, a copy could be made at the bottom and that new cell could be executed.
Doing this makes a notebook reproducible. The console has this behavior and its definitely nice being able to know when and what code was run.
The text was updated successfully, but these errors were encountered: