[sage-devel] Re: Vote for making "meataxe" optional

Hi Jeroen, On 2016-02-29, Jeroen Demeyer wrote: > On 2016-02-29 12:21, Simon King wrote: >> Interesting. I wonder how that can be debugged. I mean, it is file i/o. >> That definitely should work. > > See #20136 (I have no time to fix these issues, but that ticket should

Re: [sage-devel] Re: Vote for making "meataxe" optional

On 2016-02-29 12:21, Simon King wrote: Interesting. I wonder how that can be debugged. I mean, it is file i/o. That definitely should work. See #20136 (I have no time to fix these issues, but that ticket should contain enough information but somebody to fix it). -- You received this message

[sage-devel] Re: Vote for making "meataxe" optional

Hi Jeroen, On 2016-02-29, Jeroen Demeyer wrote: > 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: > > MeatAxe Version 2.4.24 ZZZ=ZZZ 64 Feb 29 2016 10:17:31

[sage-devel] Re: Vote for making "meataxe" optional

Hi Jeroen, On 2016-02-29, Jeroen Demeyer wrote: > 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 Yes. But

[sage-devel] Re: Vote for making "meataxe" optional

On Sunday, February 28, 2016 at 10:11:24 AM UTC, mmarco wrote: > > I definitely vote for making it optional, and try to make it standard soon. me too. > Unless the code you wrote with Martin gets finished and proves to be > better, of course. > -- You received this message because you

[sage-devel] Re: Vote for making "meataxe" optional

On 2016-02-28, Simon King wrote: > I had to patch the upstream sources considerably. > - One patch prevents that MeatAxe writes multiplication tables into the > current directory. Upstream claims that setting an appropriate > environment variable would be enough for

[sage-devel] Re: Vote for making "meataxe" optional

Hi David, On 2016-02-28, David Roe 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 >