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

>If someone who knows what they are talking about [...] to give a precise answer to the question on https://ask.sagemath.org/

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

as far as I know, limiting to 16 bit exponents for _input_ was introduced > to prevent undetected overflows; > it must be one of the tickets >> >> >> If someone who knows what they are talking about (i.e., not me) could mention this on the ask.sagemath question that would be really helpful.

Re: [sage-devel] Too many Maximas!

On Wed, Feb 8, 2017 at 11:07 AM, Ralf Stephan wrote: > On Wednesday, February 8, 2017 at 4:58:26 PM UTC+1, kcrisman wrote: >> >> But there is no reason to *remove* the pexpect, just to make Sage not >> dependent upon it for any "normal" operations. > > > You mean we should leave its dead code in S

Re: [sage-devel] Too many Maximas!

On Wednesday, February 8, 2017 at 4:58:26 PM UTC+1, kcrisman wrote: > > But there is no reason to *remove* the pexpect, just to make Sage not > dependent upon it for any "normal" operations. > You mean we should leave its dead code in Sage when we're done, just to make sure porting stays inheren

Re: [sage-devel] Too many Maximas!

> To answer this question for myself--as the discussion on what Maxima > is used for in Sage pointed me in the right direction--the > sage/calculus tests reliably start up at least 3 maxima processes, > which then run away with my CPU even after the those tests are > finished. I'll see if I

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

as far as I know, limiting to 16 bit exponents for _input_ was introduced to prevent undetected overflows; it must be one of the tickets https://www.singular.uni-kl.de:8005/trac/ticket/630 https://www.singular.uni-kl.de:8005/trac/ticket/631 https://www.singular.uni-kl.de:8005/trac/ticket/696 http

[sage-devel] Re: GSoC 2017 kickoff

I have an idea for a project but no time this year for mentoring (maybe next one) The idea boils down to develop a random testing framework to find (in some way minimal) failing examples (wrong answers or crashes) using bots (like running patchbot to test sage). So if someone is willing, able

[sage-devel] Re: GSoC 2017 kickoff

On Wednesday, February 8, 2017 at 11:03:57 AM UTC, David Coudert wrote: > > That's clearly something we need. > If the student is good and fast, (s)he can also try to implement the > split-decomposition which is a generalization of modular decomposition that > can be computed in linear time (ro

[sage-devel] Re: GSoC 2017 kickoff

That's clearly something we need. If the student is good and fast, (s)he can also try to implement the split-decomposition which is a generalization of modular decomposition that can be computed in linear time (roughly finds complete bipartite graph separators). Also, we could consider adding e

Re: [sage-devel] Too many Maximas!

On Wed, Feb 8, 2017 at 10:36 AM, Erik Bray wrote: > On Tue, Feb 7, 2017 at 6:49 PM, Jeroen Demeyer wrote: >> 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

Re: [sage-devel] Too many Maximas!

On Tue, Feb 7, 2017 at 6:49 PM, Jeroen Demeyer wrote: > 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 wi

Re: [sage-devel] Too many Maximas!

On Tue, Feb 7, 2017 at 9:35 PM, Jean-Pierre Flori wrote: > 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

Re: [sage-devel] Experience from Sage Review Day 3: An online hacking event

Hi, Thanks Johan for this summary. I definitely second your statement: it was a successful meeting with a very high output / organization overhead ratio. For those interested in the details of this output: - the framapad: https://bimestriel.framapad.org/p/SageReviewDay3 - trac tickets with key

[sage-devel] Experience from Sage Review Day 3: An online hacking event

Hi sage-devel Yesterday we held Sage Review Day 3, and it was a big success. I just wanted to briefly share my experience with this. Overall, 8 developers participated, most of them all day. We communicated using Slack, Framapad and Trac. We got 14 tickets positively reviewed, and had good progre