#13211: Upgrade GAP to 4.5.6
------------------------------------------------------------------+---------
Reporter: kini |
Owner: tbd
Type: enhancement |
Status: needs_work
Priority: major |
Milestone: sage-5.6
Component: packages |
Resolution:
Keywords: | Work
issues:
Report Upstream: Reported upstream. Developers acknowledge bug. |
Reviewers: Dmitrii Pasechnik
Authors: Volker Braun | Merged
in:
Dependencies: #13123, #13579 |
Stopgaps:
------------------------------------------------------------------+---------
Comment (by vbraun):
Replying to [comment:192 dimpase]:
> OK. Still, what about limiting the suggested_size to something (say,
500MB) - I agree that 150MB I suggested above is on a low side.
I'm against absolute limits, it should be a fraction of the available
resources. Otherwise you'll end up on record with "640kb is enough for
everyone".
> Anyway, we should put somewhere in the documentation a remark that by
default such-and-such max amount is allocated, but if you need more, then
do {{{set_gap_memory_pool_size()}}} before doing any GAP stuff.
Its in the `set_gap_memory_pool_size` docstring already.
> By the way, can one terminate, from Sage, all the running GAP
subprocesses?
The Sage expect interface does not keep a list of started subprocesses, so
no. That would be a nice enhancement to the whole expect stuff, but please
in another ticket.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13211#comment:193>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
