SUMMARY Once you hit a syntax error, the session is totally broken with no way to recover other than restarting the kernel STEPS TO REPRODUCE 1. evaluate "exp(1))" 2. watch a syntax error 3. evaluate the corrected expression "exp(1)" 4. watch a syntax error again 5. evaluate any other expression 6. watch a syntax error again 7. restart the Sage kernel 8. evaluate any expression 9. works SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.9.8 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1
A possibly relevant merge request was started @ https://invent.kde.org/education/cantor/-/merge_requests/22
Created attachment 133329 [details] Cantor info
Created attachment 133330 [details] First execution
Created attachment 133331 [details] Second execution
Interesting, because I can't reproduce it with 20.11.80 on Ubuntu 20.04. (I have a problem with creating desktop recording, so I have just make a few screenshots)
sage 9.1 used a very old ipython version, which probably behaves differently.
You use sage 9.2?
(In reply to Nikita Sirgienko from comment #7) > You use sage 9.2? Yes, but I could also reproduce it with the distro Sage 9.1 package built against ipython 7
Ok. I also reproduce it with Sage 9.2 on Ubuntu 20.10
Git commit 7abf57f88ba69883237d84c82db3f195eb961693 by Antonio Rojas. Committed on 14/11/2020 at 15:48. Pushed by arojas into branch 'release/20.12'. Fix unusable Sage session after a syntax error When we are thrown to the additional input prompt, simply report and error and send an interrupt signal to exit. Do not try to guess what the problem is and fix it: this might be caused by an unmatched opening bracket or closing bracket, in which case we would be stuck in the additional input prompt forever M +2 -2 src/backends/sage/sageexpression.cpp https://invent.kde.org/education/cantor/commit/7abf57f88ba69883237d84c82db3f195eb961693