Le mar. 19 févr. 2019 à 23:39, Nils Bruin a écrit :
>
> On Tuesday, February 19, 2019 at 2:04:54 PM UTC-8, slelievre wrote:
>>
>> but how does one get information in a Maxima session about settings
>> such as besselexpand, display2d, domain, keepfloat,
>
> These are just global variables, so
On Tuesday, February 19, 2019 at 2:04:54 PM UTC-8, slelievre wrote:
>
> but how does one get information in a Maxima session about settings
> such as besselexpand, display2d, domain, keepfloat,
>
These are just global variables, so "display2d;" will give you the value.
> and loaded
> modules
Tue 2019-02-19 08:20:24 UTC+1, Enrique Artal:
>
> I'll do it, but anyway it is strange that the wrong result
> is not reproduced using sage -maxima.
Running `sage --maxima` (or `sage -maxima`) in a terminal
launches plain Maxima, with Maxima's default settings.
When Sage perform some symbolic
This is a known issue with the conda package as the sage package hasn't
been updated yet for the new compiler runtimes on conda-forge.
Try,
conda create -n sage sage -c conda-forge/label/cf201901
Isuru
On Tue, Feb 19, 2019 at 1:11 PM Douglas Webster <
douglas.webster2...@gmail.com> wrote:
>
>
Operating system: See Attached file.
I installed Sage using conda giving the following commands during the
session as per the instructions on the sage website:
conda update --all
anaconda-navigator
conda create -n sage sage
conda activate sage
sage
I then removed the conda environment and
On Tuesday, February 19, 2019 at 8:56:50 AM UTC-8, Michael Beeson wrote:
>
> When I try to reproduce Eric's post, I get an error message about an
> unexpected keyword argument
> (maybe my version of Sage is too old.) But look at this:
>
> sage:
When I try to reproduce Eric's post, I get an error message about an
unexpected keyword argument
(maybe my version of Sage is too old.) But look at this:
sage: solve(*2**(x+sqrt(*1*-x^*2*))-*7*,x,explicit_solutions=True)
[1/4*I*sqrt(41) + 7/4 == -1/2*sqrt(7/2*I*sqrt(41) + 2), 1/4*I*sqrt(41)
Please supply details about your system (and note that we do not
really can offer support for Sagemath 7.* versions). Did you set any
SAGE-specific environment variables before starting the build?
(It looks as if you set SAGE_ROOT to some value, like "/", something
that you should not do)
On Tue,
Dear all,
Please find the full mesg. text below. the log file is attached.
Best,
Akshay.
...
XDG_SESSION_TYPE=x11
XDG_VTNR=1
XMODIFIERS=@im=none
***
make[1]: Entering directory `/home/ap/Documents/sage/sage-7.6/build/make'
make base
make[2]:
