Just to point out the obvious, the error is almost at 2^32 so it is a
problem with large file support.
On Monday, February 29, 2016 at 10:19:49 AM UTC+1, Jeroen Demeyer wrote:
>
> Test 0222: File i/o: integer
> *** ERROR:Unexpected value 4294898226 at position 1
>
--
You received this messag
On 2016-02-28 10:49, Simon King wrote:
I'd also like to ask people to test the package on a range of platforms.
The meataxe testsuite fails on powerpc64le:
Host system:
Linux sardonis 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:13 UTC
On 2016-02-28 10:49, Simon King wrote:
Recently, a "MeatAxe" package was added to Sage. Currently, it is
experimental
Really?
jdemeyer@sardonis:~/sage-check$ cat build/pkgs/meataxe/type
optional
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
On 2016-02-28 10:49, Simon King wrote:
Hi!
Recently, a "MeatAxe" package was added to Sage. Currently, it is
experimental --- based on my mistaken assumption that a new package
should first be experimental before it can be made optional.
The only difference between optional and experimental is
On Sun, Feb 28, 2016 at 10:49:21AM -0500, David Roe wrote:
>On Sun, Feb 28, 2016 at 5:11 AM, mmarco <[1]mma...@unizar.es> wrote:
> I definitely vote for making it optional, and try to make it
> standard soon.
>
>Agreed. I'm also interested in the modular representation part of
>
On Sun, Feb 28, 2016 at 5:11 AM, mmarco wrote:
> I definitely vote for making it optional, and try to make it standard soon.
>
Agreed. I'm also interested in the modular representation part of
meataxe. Is that functionality exposed in the current package or will that
require more Cython wrappe
I definitely vote for making it optional, and try to make it standard soon.
Unless the code you wrote with Martin gets finished and proves to be better, of
course.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group an
Hi!
Recently, a "MeatAxe" package was added to Sage. Currently, it is
experimental --- based on my mistaken assumption that a new package
should first be experimental before it can be made optional.
So, I'm asking here whether MeatAxe should become "optional". I actually
wouldn't mind about "stan