[sage-devel] ulimit issues and IPython 5.0

I start a new thread in this list as a continuation of "How to limit heavy computations" in sage-support. I try to summarize the problem. In my University, we have two servers to run math labs; it is done in several instances of sagenb using server_pool to enhance (at least a little bit)

Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

I recently updated Sage to version 7.5.1 (from the ppa) and although the behavior is still the same, a new warning message might give us some insight: /usr/lib/sagemath/local/lib/python2.7/site-packages/psutil/_pslinux.py:364: RuntimeWarning: 'sin' and 'sout' swap memory stats couldn't be

Re: [sage-devel] Too many Maximas!

On Tuesday, February 7, 2017 at 5:47:40 PM UTC+1, William wrote: > > Basic question: is there any reason whatsoever for us to even have a > pexpect interface to maxima anymore? Please see https://trac.sagemath.org/wiki/symbolics/maxima and the metaticket https://trac.sagemath.org/ticket/17753

[sage-devel] Re: GSoC 2017 kickoff

On Tuesday, February 7, 2017 at 11:13:40 PM UTC+1, mmarco wrote: > > I don't plan to have much time available to mentor, but I think the > project of porting rubi to sage would be doable. Someone wants to step in > as a co-mentor? > No GSoC commitment from me but a support statement. -- You

Re: [sage-devel] Too many Maximas!

On Tuesday, February 7, 2017 at 2:12:30 PM UTC-8, William wrote: > > On Tue, Feb 7, 2017 at 5:08 PM, Nils Bruin > wrote: > > On Tuesday, February 7, 2017 at 8:47:40 AM UTC-8, William wrote: > >> > >> > >> Basic question: is there any reason whatsoever for us to even have a

Re: [sage-devel] Too many Maximas!

On Tue, Feb 7, 2017 at 5:08 PM, Nils Bruin wrote: > On Tuesday, February 7, 2017 at 8:47:40 AM UTC-8, William wrote: >> >> >> Basic question: is there any reason whatsoever for us to even have a >> pexpect interface to maxima anymore? Nils Bruin (and others) put a >> massive

Re: [sage-devel] Too many Maximas!

On Tuesday, February 7, 2017 at 8:47:40 AM UTC-8, William wrote: > > > Basic question: is there any reason whatsoever for us to even have a > pexpect interface to maxima anymore? Nils Bruin (and others) put a > massive amount of effort into a C library version (using ecl) over the > years...

Re: [sage-devel] Too many Maximas!

Our pexpect interface happily leaves zombies around on linux because it never waits on the processes it forks. At least for each instantiation of the pexpect class it tries to launch sage-cleaner to have at least one instance running and only the first does actual work, the other ones becoming

[sage-devel] Re: a 7(!) year old (Singular) overflow issue still holds

Probably closely related: https://ask.sagemath.org/question/36480/restricted-usability-of-singular-after-upgrade/ -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-devel] Re: GSoC 2017 kickoff

I've added a project on modular decomposition of graphs and digraphs. How many more we would like to have? On Thursday, January 19, 2017 at 6:05:19 PM UTC, Harald Schilly wrote: > > Hello, this year's Google Summer of Code 2017 just started. > > I assume we will try again to be part of it, and

Re: [sage-devel] Too many Maximas!

On 2017-02-07 17:30, Erik Bray wrote: A problem I've been having lately when running Sage's test suite on Cygwin (i.e. sage -t -a). Several of the tests that use Maxima are spinning up Maxima processes (I guess interacted with via pexpect?) and not killing them. This is probably

Re: [sage-devel] Too many Maximas!

On 2017-02-07 17:46, William Stein wrote: Basic question: is there any reason whatsoever for us to even have a pexpect interface to maxima anymore? Nils Bruin (and others) put a massive amount of effort into a C library version (using ecl) over the years... Basic answer: there are tons of

Re: [sage-devel] Too many Maximas!

> On this I have no idea. It might be that the pexpect interface is > retained for backwards compat, and that the tests for it are causing > problems. But I don't know--this is why I'm asking. That is my understanding/guess, and we could probably deprecate it or consider it

Re: [sage-devel] Too many Maximas!

On Tue, Feb 7, 2017 at 5:46 PM, William Stein wrote: > On Tue, Feb 7, 2017 at 11:30 AM, Erik Bray wrote: >> A problem I've been having lately when running Sage's test suite on >> Cygwin (i.e. sage -t -a). >> >> Several of the tests that use Maxima are

Re: [sage-devel] Too many Maximas!

On Tue, Feb 7, 2017 at 11:30 AM, Erik Bray wrote: > A problem I've been having lately when running Sage's test suite on > Cygwin (i.e. sage -t -a). > > Several of the tests that use Maxima are spinning up Maxima processes > (I guess interacted with via pexpect?) and not

[sage-devel] Too many Maximas!

A problem I've been having lately when running Sage's test suite on Cygwin (i.e. sage -t -a). Several of the tests that use Maxima are spinning up Maxima processes (I guess interacted with via pexpect?) and not killing them. And what's worse, is that each one seems to sit in a busy wait. So

[sage-devel] Re: GSoC 2017 kickoff

On Tuesday, February 7, 2017 at 9:33:22 AM UTC-6, Travis Scrimshaw wrote: > > I added two projects with the somewhat broad subject areas: > > - Improve the representation theory in Sage > - Improve the root system code in Sage > > I added another one for quantum cluster algebras (based on a

[sage-devel] Re: GSoC 2017 kickoff

I added two projects with the somewhat broad subject areas: - Improve the representation theory in Sage - Improve the root system code in Sage -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

[sage-devel] Re: cc1 killed in iMac

> > Btw, what is the oldest and slowest computer where SageMath currently can > be compiled (without docs, as docbuilding should preferably be done in a > supercomputer near you...)? > > Slowest is almost certainly a Raspberry Pi with compile times in the multiple days (to a week)? Best,

[sage-devel] Python3 regressions

On 2017-01-19 08:47, Frédéric Chapoton wrote: We need to have the doctest framework itself check that there is no bad print and a few other solved issues. I have required help to do that, but nobody stepped in. I think that this is just not easy to do. Are the issues that you have in mind

[sage-devel] Re: cc1 killed in iMac

On Tuesday, February 7, 2017 at 6:58:22 AM UTC, Jori Mäntysalo wrote: > > Just for fun I tried to compile SageMath on an old iMac with 1 GB RAM and > 2 x T7400 Intel Core 2. > > It stops when compiling m4rie, see > http://www.sis.uta.fi/~jm58660/m4rie-20150908.txt for a full log. Error >

Re: [sage-devel] cc1 killed in iMac

On Tue, 7 Feb 2017, Jeroen Demeyer wrote: It stops when compiling m4rie, see http://www.sis.uta.fi/~jm58660/m4rie-20150908.txt for a full log. Error message is gcc: internal compiler error: Killed (program cc1) Most likely, this is because your system ran out of memory (check dmesg to be

Re: [sage-devel] cc1 killed in iMac

On 2017-02-07 07:58, Jori Mäntysalo wrote: Just for fun I tried to compile SageMath on an old iMac with 1 GB RAM and 2 x T7400 Intel Core 2. It stops when compiling m4rie, see http://www.sis.uta.fi/~jm58660/m4rie-20150908.txt for a full log. Error message is gcc: internal compiler error: