-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Scripts run in interactive mode exit on Error #21233
Labels
minor change
Marginal behavior change acceptable for a minor release
REPL
Julia's REPL (Read Eval Print Loop)
Comments
I also had this expectation. |
I gather from this comment that it is the intended behavior. Is there any chance that can be changed? Otherwise I should just close this. |
Yes I think this could be changed. |
JeffBezanson
added
REPL
Julia's REPL (Read Eval Print Loop)
triage
This should be discussed on a triage call
minor change
Marginal behavior change acceptable for a minor release
and removed
triage
This should be discussed on a triage call
labels
Sep 7, 2018
Triage accepts. |
Awesome! Thank you very much! |
JeffBezanson
added a commit
that referenced
this issue
Nov 29, 2018
JeffBezanson
added a commit
that referenced
this issue
Nov 30, 2018
staticfloat
pushed a commit
that referenced
this issue
Jan 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
minor change
Marginal behavior change acceptable for a minor release
REPL
Julia's REPL (Read Eval Print Loop)
If a script is run in interactive mode:
julia -i myscript.jl arg1 arg2
and it encounters an error, julia exits.
It's as if the script first runs normally, then after it finishes the REPL starts.
I expected (coming from Python) that it would as if the REPL was running the script line-by-line. In that case, the REPL would not exit after an error and let me examine the variables, try to correct the error interactively, etc.
My apologies if it is the intended behavior or if it was discussed before. I couldn't find anything.
The text was updated successfully, but these errors were encountered: