[sage-devel] Re: failures on 8.3.beta3 (probably due to meataxe?)

2018-05-31 Thread Nils Bruin
On Thursday, May 31, 2018 at 12:20:49 PM UTC-7, Simon King wrote: > > If I understand correctly, when using rescale_row in a schoolbook > implementation of gaussian elimination, it is certainly the case that > the leading columns are zero. But would it be ok to state this > assumption in the doc

Re: [sage-devel] Re: python3 status

2018-05-31 Thread Emmanuel Charpentier
Dear Nils, Le jeudi 31 mai 2018 18:31:31 UTC+2, Nils Bruin a écrit : > > On Thursday, May 31, 2018 at 4:52:04 AM UTC-7, Emmanuel Charpentier wrote: >> >> I'm grabbing the opportunity to recall that , whereas I have installed >> the Sage kernel in my (systemwide) jupyter installation via the suita

[sage-devel] Re: failures on 8.3.beta3 (probably due to meataxe?)

2018-05-31 Thread Simon King
On 2018-05-31, Simon King wrote: > In fact I have a question on the API. If M.rescale_row_c(i,s,start_col) > is called, is it assumed that items 0,...,start_col-1 are zero in row > number i of M? I was looking at the implementation in sage/matrix/matrix0.pyx. There is actually no test demonstrati

Re: [sage-devel] Re: python3 status

2018-05-31 Thread Matthias Koeppe
I have created https://trac.sagemath.org/ticket/25486 for this. On Wednesday, May 30, 2018 at 10:32:42 AM UTC-7, Matthias Koeppe wrote: > > On Wednesday, May 30, 2018 at 9:01:59 AM UTC-7, Nils Bruin wrote: >> >> >> Currently, if I run the script $SAGE_LOCAL/bin/sage in my normal >> environment (w

[sage-devel] Re: failures on 8.3.beta3 (probably due to meataxe?)

2018-05-31 Thread Simon King
Hi Travis, first of all: Thank you for figuring out the problem. On 2018-05-31, Travis Scrimshaw wrote: > I have figured out what was going wrong: after #17272, the *generic* > algorithm was being called rather than the specific implementation, which > was still called _echelon_in_place_classi

Re: [sage-devel] Re: python3 status

2018-05-31 Thread Nils Bruin
On Thursday, May 31, 2018 at 4:52:04 AM UTC-7, Emmanuel Charpentier wrote: > > I'm grabbing the opportunity to recall that , whereas I have installed the > Sage kernel in my (systemwide) jupyter installation via the suitable "jupyter > kernelspec install ..." invocation), when I try to use it fro

Re: [sage-devel] Re: Matrix groups are not uniquely represented, why?

2018-05-31 Thread Nils Bruin
On Thursday, May 31, 2018 at 3:05:26 AM UTC-7, Erik Bray wrote: > > > Could you actually point me to one of those memory leaks? I'm sure > they exist but I'm still not clear on how this happens. I suspect it > could be improved, and I would like to look into how... > https://trac.sagemath.o

Re: [sage-devel] Re: Matrix groups are not uniquely represented, why?

2018-05-31 Thread David Loeffler
On 31 May 2018 at 11:07, Erik Bray wrote: > > "mathematical equality" is also a red herring being that there are > many possible definitions thereof. Are we talking equality up to > isomorphism? Etc... In the example posted by Chris Wuthrich, all the objects invoved were, by construction, subg

Re: [sage-devel] Re: Matrix groups are not uniquely represented, why?

2018-05-31 Thread Nils Bruin
On Thursday, May 31, 2018 at 3:07:11 AM UTC-7, Erik Bray wrote: > > > "mathematical equality" is also a red herring being that there are > many possible definitions thereof. Are we talking equality up to > isomorphism? Etc... > In this case it is not: presenting a group as a matrix groups mean

Re: [sage-devel] Re: python3 status

2018-05-31 Thread Emmanuel Charpentier
I'm grabbing the opportunity to recall that , whereas I have installed the Sage kernel in my (systemwide) jupyter installation via the suitable "jupyter kernelspec install ..." invocation), when I try to use it from the systemwide jupyter via the "normal" invocation "jupyter notebook", it compl

[sage-devel] Re: failures on 8.3.beta3 (probably due to meataxe?)

2018-05-31 Thread Travis Scrimshaw
I have figured out what was going wrong: after #17272, the *generic* algorithm was being called rather than the specific implementation, which was still called _echelon_in_place_classical. I have added a _echelon_in_place to the meataxe matrices to simply call this. We probably should have desi

Re: [sage-devel] Re: Matrix groups are not uniquely represented, why?

2018-05-31 Thread Erik Bray
On Wed, May 30, 2018 at 8:14 AM, Travis Scrimshaw wrote: > > > On Tuesday, May 29, 2018 at 9:01:51 PM UTC+10, chris wuthrich wrote: >> >> >> As a simple-minded user I stumbled over exactly this last week. I don't >> understand much of what this thread is discussing, but I know what a >> simple-min

Re: [sage-devel] Re: Matrix groups are not uniquely represented, why?

2018-05-31 Thread Erik Bray
On Mon, May 28, 2018 at 6:11 PM, Nils Bruin wrote: > On Monday, May 28, 2018 at 7:24:31 AM UTC-7, Simon King wrote: >> >> However, I find your notion of immutability ("do not allow assigning >> attributes and make all existing attributes immutable") far too narrow. >> IIRC, immutable means that on

[sage-devel] Re: failures on 8.3.beta3 (probably due to meataxe?)

2018-05-31 Thread Simon King
Hi Vincent, On 2018-05-31, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > I have no idea which ticket introduced this change but it used to work > fine on beta2. Travis said it might be #17272. Anyway, I am at it, and hope to fix the problem in the next few days. Best regards, Simon --

Re: [sage-devel] Re: failures on 8.3.beta3 (probably due to meataxe?)

2018-05-31 Thread Vincent Delecroix
Dear Simon, The patchbot I run (quasar) installs all optional packages whenever they do work. It is a pain to maintain as at each beta release there is a need to disable some of them and I sometimes provide fixes. The wording might be misleading, but this is how optional packages are currently c