[sage-support] Re: Sage Crash Report

2016-03-29 Thread Volker Braun
Should be fixed in the next version. In the meantime, you can download the source tarball and compile that. On Tuesday, March 29, 2016 at 4:04:20 PM UTC+2, Oscar Alberto Castillo Felisola wrote: > > Dear community, > > lately, I'm having problems with the installation of SAGE. I downloaded >

[sage-support] Re: Sage Crash Report

2016-03-29 Thread Eric Gourgoulhon
Hi Oscar, I'm afraid I cannot help much with your specific problem. The only thing I can tell is that Sage 7.1 + SageManifolds 0.9 works well on Ubuntu, which is based on Debian, but of course differs from it. Best regards, Eric. Le mardi 29 mars 2016 16:04:20 UTC+2, Oscar Alberto Castillo F

[sage-support] Sage Crash Report

2016-03-29 Thread Oscar Alberto Castillo Felisola
Dear community, lately, I'm having problems with the installation of SAGE. I downloaded the version Sage v.7.1 for Debian_8, and it seems to work... but I installed sagemanifold v.0.9, and I got the report file attached to this post. I'm having problems too when compiling the scr code, because

Re: [sage-support] reasons for the strange behaviour of Permutations

2016-03-29 Thread Vincent Delecroix
This is indeed a bug! Thanks for the report. The thing is that the code for cardinality (before the call to .list()) is inherited from permutations without a fixed length. The (wrong) number you got (1680) is actually the number of permutations without length restriction. See http://trac

[sage-support] reasons for the strange behaviour of Permutations

2016-03-29 Thread Karol Suchan
Hi, I've spotted a strange behaviour of Permutations.cardinality(): first it reports a weird number, but after a call to list() it gets ok. Any reason why? I copy a code that compares the behaviour of Tuples, Permutations and Arrangements. %%% from sage.combinat.permutation import