On Thu, Feb 9, 2017 at 1:41 PM, Jeroen Demeyer wrote:
> On 2017-02-09 13:29, Erik Bray wrote:
>>
>> I think this can be worked
>> around in Sage by not explicitly closing the master pty until the
>> process has exited.
>
>
> I think this is doing things in the wrong order. Closing a pty is a way t
On 2017-02-09 13:29, Erik Bray wrote:
I think this can be worked
around in Sage by not explicitly closing the master pty until the
process has exited.
I think this is doing things in the wrong order. Closing a pty is a way
to signal to a process that it should exit.
This isn't Sage-specific,
On Wed, Feb 8, 2017 at 10:44 AM, Erik Bray wrote:
> 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 (
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
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
> 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
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
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
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
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
f
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
> >> pexpect in
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 amount of effort into
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...
>
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 z
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 Cygwin-specifi
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 thin
> 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 unsupported/experiment
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 spinning up Maxima processes
>> (I guess inte
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 killing them. And
> what's
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 even
20 matches
Mail list logo
