Dear all,
Sorry for the delay getting back to you -- this was waiting in the
moderation queue for a bit (me being new) and then I dropped the ball.
> run the underlying functions
>
> M = identity_matrix(n)
> L = M.list()
> MS = sage.matrix.matrix_space.MatrixSpace(GF(101), 1000, 1000,
sparse=F
On Friday, May 7, 2021 at 12:37:41 PM UTC-7 emanuel wrote:
> Nor with printed code output (see above). And it’s ugly as hell…
I guess maxima can be rather unpredictable in what whitespace it inserts.
The output that comes back is not for human consumption, but for parsing.
With just function
Le vendredi 7 mai 2021 à 17:54:51 UTC+2, Nils Bruin a écrit :
On Friday, May 7, 2021 at 6:07:30 AM UTC-7 emanuel wrote:
>
>> Both maxima interfaces mangle Maxima’s boolean operators *printing*.
>> The evaluation of a Maxima boolean expression gives nonsensical results
>> in Sage. Using the pexp
I guess you may be able to make expressions robust against space removal by
replacing "and" and "or" with non-alphanumeric "&&" and "||". Those can be
recognized also in a non-space-separated string.
Something like the following seems to do the trick:
sage: M=sage.interfaces.maxima.Maxima()
sa
On Friday, May 7, 2021 at 6:07:30 AM UTC-7 emanuel wrote:
> Both maxima interfaces mangle Maxima’s boolean operators *printing*.
> The evaluation of a Maxima boolean expression gives nonsensical results in
> Sage. Using the pexpect interface :
>
> sage: ME=maxima
>
> sage: ME("foo: a and (b or c)
This also happens in the .interact() manual interactions :
sage: ME.interact()
--> Switching to Maxima <--
maxima: foo
aand(borc)
maxima:
--> Exiting back to Sage <--
sage: MC.interact()
--> Switching to Maxima_lib <--
maxima_lib: foo
aand(borc)
maxima_lib:
--> Exiting back to Sag
This also happens in the `.interact()` manual interactions :
```
sage: ME.interact()
--> Switching to Maxima <--
maxima: foo
aand(borc)
maxima:
--> Exiting back to Sage <--
sage: MC.interact()
--> Switching to Maxima_lib <--
maxima_lib: foo
aand(borc)
maxima_lib:
--> Exiting back to
Both maxima interfaces mangle Maxima’s boolean operators *printing*.
The evaluation of a Maxima boolean expression gives nonsensical results in
Sage. Using the pexpect interface :
sage: ME=maxima
sage: ME("foo: a and (b or c)")
aand(borc)
This also happens in Maxima’s *printing*:
sage: ME("p
I added a second bijection between Dyck paths and parallelogram
polyominoes, and bijections implementing the symmetries of parallelogram
polyominoes.
The modifications are very local, all tests and linters pass. I'd be
grateful for a review.
https://trac.sagemath.org/ticket/31779
Many thanks
Hi,
On Tue, May 04, 2021 at 04:50:35PM +0100, Dima Pasechnik wrote:
> On Mon, May 3, 2021 at 10:11 AM E. Madison Bray wrote:
> >
> > On Thu, Apr 29, 2021 at 2:30 PM julian...@fsfe.org
> > wrote:
[...]
> > I've restarted the gitlab-runner service. It apparently started
> > hanging at some point
Dear all,
Substitution on multivariate polynomials is leaking memory
(https://trac.sagemath.org/ticket/27261). This can actually
crash sage if used a lot (with a memory overflow error from
singular). The code of subs and __call__ use some low-level
calls to the singular library and this is likely
11 matches
Mail list logo
