2009/11/30 William Stein wst...@gmail.com:
On Sun, Nov 29, 2009 at 9:38 AM, dimpase dimp...@gmail.com wrote:
Another similar question involves using the local version of GAP
in place of the supplied one.
Apart from the fact that Sage is distributed with an old and (a bit)
broken version of
William,
I'm curious -- what in particular is broken about GAP-4.4.10? We
tried to ship 4.4.12, but found it to be more broken; in particular,
it didn't work on Itanium Linux boxes, which is one of our officially
supported platforms.
I tried to reproduce your problem on an Itanium cluster at
Another similar question involves using the local version of GAP
in place of the supplied one.
Apart from the fact that Sage is distributed with an old and (a bit)
broken version of GAP,
(well, I know that I can install a newer version by downloading the
corresponding update)
having two copies of
If you could use the system Python, that would fix that problem too,
wouldn't it?
Tom
On Nov 29, 6:38 pm, dimpase dimp...@gmail.com wrote:
Another similar question involves using the local version of GAP
in place of the supplied one.
Apart from the fact that Sage is distributed with an old
On Sun, Nov 29, 2009 at 9:38 AM, dimpase dimp...@gmail.com wrote:
Another similar question involves using the local version of GAP
in place of the supplied one.
Apart from the fact that Sage is distributed with an old and (a bit)
broken version of GAP,
(well, I know that I can install a newer
William,
Patch 11 of GAP 4.4 fixes a dozen of critical level bugs, ie bugs
that potentially lead to wrong results! Eg getting wrong character
tables, wrong results in range intersection...
If a platform, like Itanium, was dropped, it is likely for a jolly good reason.
IMHO distributing a clearly