You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Amazing work, thanks for sharing! I've been thinking about something similar, but nodebook is an interesting alternative (and it demonstrates how to invalidate cells in jupyter).
Here's one detail that could be perhaps improved. Consider the following 4 cells:
a = 0
a += 1
a += 2
print(a)
Now proceed as following:
Evaluate all cells. The last one prints 3.
Delete the second cell.
Evaluate the last cell. It still prints 3.
If instead of deleting the cell one comments-out its contents, the behavior is as expected: the last two cells are invalidated, and upon evaluation 2 is printed. Would it be possible to do the same upon deletion? I guess that it might be tricky because of Jupyter's undo functionality.
The text was updated successfully, but these errors were encountered:
grothesque
changed the title
Cells do not get invalidated at cell removal
Cells do not get invalidated upon cell removal
Jun 28, 2018
grothesque
changed the title
Cells do not get invalidated upon cell removal
Dependent cells are not invalidated upon cell removal
Jun 29, 2018
Thanks @grothesque! I'd like to have this as a feature, but it would require tighter integration with the javascript frontend than I currently have in place.
Amazing work, thanks for sharing! I've been thinking about something similar, but nodebook is an interesting alternative (and it demonstrates how to invalidate cells in jupyter).
Here's one detail that could be perhaps improved. Consider the following 4 cells:
Now proceed as following:
If instead of deleting the cell one comments-out its contents, the behavior is as expected: the last two cells are invalidated, and upon evaluation 2 is printed. Would it be possible to do the same upon deletion? I guess that it might be tricky because of Jupyter's undo functionality.
The text was updated successfully, but these errors were encountered: