I have also noticed this problem. It seems to be caused by the upgrade to
IPython 7 https://trac.sagemath.org/ticket/28197. I have opened
https://trac.sagemath.org/ticket/30417 for this.
Andrey Novoseltsev schrieb am Donnerstag, 20. August 2020 um 23:54:52 UTC+2:
> It interferes with multiline
Thanks all for sharing your insights!
I agree that seems a good plan to wait until JupyterLab has implemented the
classic notebook. So there is no urgency in making this change.
However, we should make sure that Sage works in its entirety with
JupyterLab - ideally for Sage 9.2 already.
A key s
2020-08-21 12:40:44 UTC, Nicolo':
>
> Is there a ticket already to use python3.8 from system?
The ticket to upgrade Sage-the-distribution to Python 3.8
just got positive review:
https://trac.sagemath.org/ticket/27754
By clicking on the link in the "Branch" field one can see
that it changes `b
> I think Sage would be better off sticking with Jupyter Classic until a
> version of JupyterLab is available that can emulate Classic; otherwise, the
> interface switch will be fairly jarring to users, especially the less
> experienced ones for whom notebook interfaces are particularly appeal
I use Jupyter with Sage somewhat regularly, and have tried out JupyterLab
on several occasions. I use Jupyter notebooks only when making a lot of
plots as otherwise I prefer an editor+REPL setup. In particular, I have
not used it in any of my classes.
As mentioned, JupyterLab is more like an
Finally sage builds successfully on void linux :)
I will add spkg files for pari-seadata etc as soon as the packages are
approved, this way it does not have to build pari and giac.
Is there a ticket already to use python3.8 from system?
Should I be worried that it fails some doctest?
sage -t
