-
Notifications
You must be signed in to change notification settings - Fork 17
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
Should code after %save be executed? #180
Comments
Yes that was indeed in some of my old code.
I used it heavily before because it looks nice on github -- I have one file for lots of scripts. But it is about the only benefit of it. Offline I use If you ask my personal opinion of reverting: the major impact is that it will break one of my project (with a paper under review) but I'd not worry about it because I do not think they will ever try to reproduce it and even if they do, my official instruction was to use a docker image I made. Also this will impact some code @minqiao has but it is not a big deal. So it's Okay if you want to change the behavior back and we'll make adjustments accordingly. |
I do not get it. github does not highlight sos notebook, right? Or are you saying |
Sorry -- I never use |
So perhaps a |
Sure, thanks! Yes although I'm neutral at this point, if down the line we do improve the syntax highlighting and other features and somehow make SoS notebook a decent script organizer this magic might then be useful to have. Also |
With #179 , I am adding a new
%runfile
magic that uses thepattern to replace
However, the current behavior of
%save
is that it will save the cell without executing them, so the above example will not work.will not work either because
%run
will send%save
to sos command.I remember that we had this discussion a long time ago and you seem to use
%save
to create multiple workflows or arbitrary config file so you prefer the current behavior (of not executing the rest of the cell). Is this still the case?I think using
%save
to make Jupyter an editor of external file is logically suspicious, and we already havefor this purpose. Should I change the behavior back?
The text was updated successfully, but these errors were encountered: