[sage-devel] Re: Can we get rid of the "Consider using a block-scoped tag" warning?

On Friday, August 4, 2023 at 1:54:53 AM UTC+9 Volker Braun wrote: The test output is full of "Warning: Consider using a block-scoped tag by inserting the line...", making it hard to see where the actual error is. I agree. Hopefully, the warnings would be removed soon if more people work on

Re: [sage-devel] Re: Memory leak (quite bad)

is it related to https://github.com/sagemath/sage/issues/27185 ? and/or https://github.com/sagemath/sage/issues/19363 pynac is a worry. On Thu, 3 Aug 2023, 23:59 Volker Braun, wrote: > A quick valgrind run for > > from sage.all import sqrt > T2 = sqrt(2) > for b in range(num := 100

[sage-devel] Re: Memory leak (quite bad)

A quick valgrind run for from sage.all import sqrt T2 = sqrt(2) for b in range(num := 100_000): C = sqrt(T2) confirms that it is in pynac: ==3947957== 799,912 bytes in 99,989 blocks are definitely lost in loss record 1,299 of 1,300 ==3947957==at 0x484182F: malloc (vg_re

[sage-devel] Re: Can we get rid of the "Consider using a block-scoped tag" warning?

On Thursday, August 3, 2023 at 9:54:53 AM UTC-7 Volker Braun wrote: The test output is full of "Warning: Consider using a block-scoped tag by inserting the line...", making it hard to see where the actual error is. Whats the purpose of this? Is somebody working on converting the magic comments

[sage-devel] Can we get rid of the "Consider using a block-scoped tag" warning?

The test output is full of "Warning: Consider using a block-scoped tag by inserting the line...", making it hard to see where the actual error is. Whats the purpose of this? Is somebody working on converting the magic comments? Should the warning be unconditionally removed? Can it at least be

[sage-devel] Re: Synchronization of GitHub state and priority labels starts on Tuesday July 18th

I've added a comment to issue #35927 to enable a next step accordingly. More information about what will change in this step can be found there. Kwankyu Lee schrieb am Donn