Re: [sage-devel] Re: Python 3: gap interface issue

2019-02-06 Thread Nathan Dunfield
On Monday, February 4, 2019 at 8:12:02 AM UTC-6, Nathan Dunfield wrote: > > On Sunday, February 3, 2019 at 10:31:21 PM UTC-6, Dima Pasechnik wrote: >> >> I don't know what exactly is wrong with that docker container, but >> certainly GAP workspace might not be present if you never ran GAP via >

Re: [sage-devel] Re: Python 3: gap interface issue

2019-02-06 Thread Kiran Kedlaya
I would definitely appreciate getting deprecation messages in calls to gap(...) as soon as possible! Kiran On Monday, February 4, 2019 at 7:18:31 AM UTC-8, E. Madison Bray wrote: > > On Mon, Feb 4, 2019 at 2:23 AM Simon King > wrote: > > > Is the plan to make > > > "gap" and alias of (or a wr

Re: [sage-devel] AlarmInterrupt causes Sage to crash hard

2019-02-06 Thread Nils Bruin
On Wednesday, February 6, 2019 at 6:35:27 AM UTC-8, E. Madison Bray wrote: > > > Which is being reached because AlarmInterrupt is a subclass of > KeyboardInterrupt . I don't know why this doesn't happen then when, > say, mashing Ctrl-C. I guess because IPython installs its own SIGINT > handle

Re: [sage-devel] AlarmInterrupt causes Sage to crash hard

2019-02-06 Thread E. Madison Bray
On Wed, Feb 6, 2019 at 10:29 AM jonathan.kliem via sage-devel wrote: > > sage: alarm(1) > sage: > > AlarmInterrupt escaped interact() > > sage: > sage: > ^[[50;1R > ** > > Oops, Sage crashed. We do our best to make it stable, but.

Re: [sage-devel] libgap does not free memory after hitting the memory limit

2019-02-06 Thread E. Madison Bray
On Wed, Feb 6, 2019 at 10:46 AM Dima Pasechnik wrote: > > On Wed, Feb 6, 2019 at 9:16 AM Simon Brandhorst wrote: > > > > After running > > > > sage: V = libgap.GF(3)^2000 > > sage: libgap(V.Subspaces(1000)).List() > > --- > >

[sage-devel] SageNB and Firefox

2019-02-06 Thread TAU
(I know, I know... SageNB is deprecated.) In the newest firefox in Linux pressing backspace in an empty cell does not delete the input cell. It works in Chromium. Why that, any workaround on the server side? -- Jori Mäntysalo Tampereen yliopisto - Ihminen ratkaisee -- You received this mess

Re: [sage-devel] libgap does not free memory after hitting the memory limit

2019-02-06 Thread Dima Pasechnik
On Wed, Feb 6, 2019 at 9:16 AM Simon Brandhorst wrote: > > After running > > sage: V = libgap.GF(3)^2000 > sage: libgap(V.Subspaces(1000)).List() > --- > ValueErrorTraceback (most recent call la

Re: [sage-devel] libgap does not free memory after hitting the memory limit

2019-02-06 Thread Dima Pasechnik
Try sage: libgap.eval('GASMAN("collect")') - at least this is something one would do in a GAP interative session, gap> GASMAN("collect"); On Wed, Feb 6, 2019 at 9:16 AM Simon Brandhorst wrote: > > After running > > sage: V = libgap.GF(3)^2000 > sage: libgap(V.Subspaces(1000)).List() > ---

[sage-devel] AlarmInterrupt causes Sage to crash hard

2019-02-06 Thread jonathan.kliem via sage-devel
sage: alarm(1) sage: AlarmInterrupt escaped interact() sage: sage:

[sage-devel] libgap does not free memory after hitting the memory limit

2019-02-06 Thread Simon Brandhorst
After running sage: V = libgap.GF(3)^2000 sage: libgap(V.Subspaces(1000)).List() --- ValueErrorTraceback (most recent call last) . ValueError: libGAP: Error, reached the pre-set memory limit