As Dima said, please report bugs of distribution packaging of Sage to the
distribution.
On Monday, February 1, 2021 at 8:29:17 AM UTC-8 tiger...@gmail.com wrote:
> I should also add this.
> If from an ipython module I invoke `from sage.misc.misc_c import prod`,
> everything works fine.
> On
I should also add this.
If from an ipython module I invoke `from sage.misc.misc_c import prod`,
everything works fine.
On the other hand, `from sage.rings.all import RealField` works well inside
ipython, but produce a different error from a source file.
Relevant link
This has to be reported to Arch people.
On Mon, Feb 1, 2021 at 1:39 PM Simone Perriello wrote:
>
>
> Operating system: ArchLinux.
> Sage installed through official packages.
> If I just launch `sage` from terminal it gives this stacktrace
> https://pastebin.com/s1FnMhe2
>
> The same happens if
Operating system: ArchLinux.
Sage installed through official packages.
If I just launch `sage` from terminal it gives this stacktrace
https://pastebin.com/s1FnMhe2
The same happens if I try to do a `from sage.all import *` from ipython,
from a python file or from sage -python.
--
You
On Mon, Feb 1, 2021 at 10:22 AM Derick Swodnick wrote:
>
> Hello! I am trying to build from Sage source code in Ubuntu, but
> unfortunately I get this error.
>
>
> [..]
> rm -f config.log
> mkdir -p logs/pkgs
> ln -s
On Mon, Feb 1, 2021 at 6:36 AM dan hayes wrote:
>
> i have heard running in WSL are slower and extra delays compared to other
> possibilities. If nothing else and i ended up buying one of those advertised
> "Xtra-PC" usb's already with linux is it easy to insall sagemath on one of
> those ?
Hello! I am trying to build from Sage source code in Ubuntu, but
unfortunately I get this error.
[..]
rm -f config.log
mkdir -p logs/pkgs
ln -s logs/pkgs/config.log config.log
