Re: [sage-devel] ping - please cast you vote: VOTE: Follow NEP 29: Recommended Python version

[Tobias Diez]

On Thursday, 6 July 2023 at 23:25:12 UTC+2 Nils Bruin wrote:

It looks to me proposal 1 still doesn't make it *mandatory* to drop support 
outside of the NEP29-defined version window. It seems to me that it just 
defines when a support-drop PR becomes acceptable to merge, and that such a 
PR would only be issued once someone feels there's a benefit to its merge.

If that interpretation is right, it seems to me that the difference between 
proposal 1 and proposal 2 will only be relevant if there is a PR to drop a 
python version V (outside of the NEP29 window) and there is someone else 
who want to keep support for that version V. With proposal 2 we'd get a 
discussion of the relevant pros and cons. With proposal 1, there'd normally 
not be a discussion at this point: version V is fair game to be dropped. 
There could still be a discussion if someone claims there's an exceptional 
circumstance that warrants deviating from official policy, but that would 
have a much higher bar to clear.


Yes, this interpretation is what I had in mind. 
 

>From the perspective above, Proposal 1 seems more attractive to me than 
Proposal 2, since it avoids extra discussion with what seems a very 
reasonable default policy (the NEP 29 window seems wide enough to me). 


For me, this is the main advantage of having a policy about the drop 
schedule. We can now have a dedicated conversation to thoroughly explore 
the pros and cons, to consider various perspectives, gather feedback, and 
make an informed decision. Once a policy has been established and agreed 
upon, it provides a clear framework that eliminates the need for repetitive 
discussions and debates about dropping specific policies in every PR again. 



-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/56b2148c-7b22-4631-ba7c-2e931ae03bc3n%40googlegroups.com.

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

[Georgi Guninski]

Simpler testcase is to replace `C = sqrt(T2)`
with `C=SR(int(2)).sqrt()`
Both int() and sqrt() appear necessary, sin() doesn't leak for me.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGUWgD-Zbqzu2RzCZ7DYbtzPDDD9i1SX3zh%3DexL2xwNOcYcL2A%40mail.gmail.com.

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

[Edgar Costa]

Nils,

This is my recommendation to avoid my worst-case scenario, where someone
must go to some far away basement and power cycle the server manually after
waiting a couple of days for OOM kicking in.
I'm okay with a user using 90% of the ram, if that becomes an issue, I can
always email them or kill their process, but more often than not, until I
started to use earlyoom is that the memory usage slowly creeps to 100% and
the culprit process only gets killed by oom or a power cycle.

Cheers,
Edgar

On Thu, Jul 6, 2023 at 8:56 PM Michael Orlitzky 
wrote:

> On 2023-07-06 09:16:46, Nils Bruin wrote:
> > > On Wednesday, 5 July 2023 at 08:29:44 UTC-7 Edgar Costa wrote:
> > >
> > > Hi Gonzalo,
> > >
> > > I highly recommend using https://github.com/rfjakob/earlyoom instead
> of
> > > waiting for OOM to kick in.
> >
> > Wouldn't setting ulimit with -m (memory) or -v (virtual memory) for the
> > process that is liable to exceed its memory quota be a more sensible
> thing?
>
> If you don't need a portable solution, then on linux, cgroups are the
> most flexible way to leave yourself juuust enough RAM to be able to
> move your mouse over the X.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/ZKdiwaZ8lg3aCw3K%40stitch.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5f%3DzULirZJN5K3F-grgpP6J0ee628cQKGYON_MKbbH_g%40mail.gmail.com.

[sage-devel] Re: Import module error when building documentation

[brettpim]

Matthias,  
So we should Merge your PR into the code for our PR and then merge this 
into our PR?
brett

On Thursday, July 6, 2023 at 9:12:36 PM UTC-4 brettpim wrote:

>
> Thanks Matthias!  
> brett
> On Thursday, July 6, 2023 at 5:14:34 PM UTC-4 Matthias Koeppe wrote:
>
>> It's a bug in the CI script. Merge 
>> https://github.com/sagemath/sage/pull/35865, and it will work
>>
>> On Thursday, July 6, 2023 at 1:47:06 PM UTC-7 Aaron Dwyer wrote:
>>
>>> I am attempting to add a module to sage "covering_array.py" for an open 
>>> pull request. When building documentation on the pull request I get an 
>>> error 
>>>
>>> "Warning: Could not import sage.combinat.designs.covering_array No 
>>> module named 'sage.combinat.designs.covering_array'
>>>
>>> although the file covering_array.py is in the sage/combinat/designs 
>>> folder. This error does not show up when I build documentation locally. 
>>> When run locally, the combinat section of the documentation is formatted 
>>> incorrectly however the text of the documentation in the covering_array.py 
>>> file does appear as expected. 
>>>
>>> This error was not occurring in previous versions of the PR but I cannot 
>>> tell what changed that causes it, especially since the error message is not 
>>> telling me much. 
>>>
>>> How would I fix or narrow down this error? Do I need to add a link to 
>>> the file elsewhere? 
>>>
>>> Thanks 
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/146c8ddd-620b-4506-b57b-9a1bb7ad2347n%40googlegroups.com.

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

[Nils Bruin]

On Friday, 7 July 2023 at 07:53:22 UTC-7 Edgar Costa wrote:

I'm okay with a user using 90% of the ram, if that becomes an issue, I can 
always email them or kill their process, but more often than not, until I 
started to use earlyoom is that the memory usage slowly creeps to 100% and 
the culprit process only gets killed by oom or a power cycle.

 
In that case, would you get the desired result by setting the relevant 
ulimit to 90% ? I'm trying to understand what earlyoom offers over the 
quota system that posix offers out of the box.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/83c2002f-c1fc-4a99-8b07-cc7d0957bb33n%40googlegroups.com.

[sage-devel] Re: Import module error when building documentation

[Matthias Koeppe]

That's right. If you are using the GH cli, that's "gh pr checkout 35865 && 
git checkout - && git merge -"

On Friday, July 7, 2023 at 7:55:32 AM UTC-7 brettpim wrote:

> Matthias,  
> So we should Merge your PR into the code for our PR and then merge this 
> into our PR?
> brett
>
> On Thursday, July 6, 2023 at 9:12:36 PM UTC-4 brettpim wrote:
>
>>
>> Thanks Matthias!  
>> brett
>> On Thursday, July 6, 2023 at 5:14:34 PM UTC-4 Matthias Koeppe wrote:
>>
>>> It's a bug in the CI script. Merge 
>>> https://github.com/sagemath/sage/pull/35865, and it will work
>>>
>>> On Thursday, July 6, 2023 at 1:47:06 PM UTC-7 Aaron Dwyer wrote:
>>>
 I am attempting to add a module to sage "covering_array.py" for an open 
 pull request. When building documentation on the pull request I get an 
 error 

 "Warning: Could not import sage.combinat.designs.covering_array No 
 module named 'sage.combinat.designs.covering_array'

 although the file covering_array.py is in the sage/combinat/designs 
 folder. This error does not show up when I build documentation locally. 
 When run locally, the combinat section of the documentation is formatted 
 incorrectly however the text of the documentation in the covering_array.py 
 file does appear as expected. 

 This error was not occurring in previous versions of the PR but I 
 cannot tell what changed that causes it, especially since the error 
 message 
 is not telling me much. 

 How would I fix or narrow down this error? Do I need to add a link to 
 the file elsewhere? 

 Thanks 




-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8bc11c14-e9bc-422f-99ca-07fadd6624b1n%40googlegroups.com.

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

[Edgar Costa]

Two users try to use 51% of the memory simultaneously.

On Fri, Jul 7, 2023 at 11:01 AM Nils Bruin  wrote:

> On Friday, 7 July 2023 at 07:53:22 UTC-7 Edgar Costa wrote:
>
> I'm okay with a user using 90% of the ram, if that becomes an issue, I can
> always email them or kill their process, but more often than not, until I
> started to use earlyoom is that the memory usage slowly creeps to 100% and
> the culprit process only gets killed by oom or a power cycle.
>
>
> In that case, would you get the desired result by setting the relevant
> ulimit to 90% ? I'm trying to understand what earlyoom offers over the
> quota system that posix offers out of the box.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/83c2002f-c1fc-4a99-8b07-cc7d0957bb33n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x61gLMwxf0fAVe38PirNsmxLUJ_r_DtXb2i7pq%3D19yPjw%40mail.gmail.com.

[sage-devel] Voting result: Block-scoped optional tag and the keyword

[Kwankyu Lee]

Hi,

The voting in https://groups.google.com/g/sage-devel/c/8KZNRBs6F6U is 
closed. There were 13 votes. The vote tally is as follows:

(A) "needs": 10
(B) "requires": 1
(C) "uses": 2
(D) "standard": 0

The clear winner is (A). Hence "needs" will be used as the keyword for 
block-scoped tag for optional doctests. For more, visit 
https://github.com/sagemath/sage/issues/35750.

I thank all the voters and appreciate your attention and support for smooth 
proceeding of the voting.  




-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e05cadbc-bf1d-4ce3-93dc-f098ca0ac522n%40googlegroups.com.

[sage-devel] Re: Voting result: Block-scoped optional tag and the keyword

[Kwankyu Lee]

Note that the issue #35750 is resolved by the PR at 
https://github.com/sagemath/sage/pull/35749.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/aeb2ad5d-4a01-42b5-9e77-f7a8bd22bddcn%40googlegroups.com.

[sage-devel] Re: Voting result: Block-scoped optional tag and the keyword

[Matthias Koeppe]

Thanks all for voting, and thanks Kwankyu for organizing the referendum!

Matthias

On Friday, July 7, 2023 at 3:36:33 PM UTC-7 Kwankyu Lee wrote:

> Hi,
>
> The voting in https://groups.google.com/g/sage-devel/c/8KZNRBs6F6U is 
> closed. There were 13 votes. The vote tally is as follows:
>
> (A) "needs": 10
> (B) "requires": 1
> (C) "uses": 2
> (D) "standard": 0
>
> The clear winner is (A). Hence "needs" will be used as the keyword for 
> block-scoped tag for optional doctests. For more, visit 
> https://github.com/sagemath/sage/issues/35750.
>
> I thank all the voters and appreciate your attention and support for 
> smooth proceeding of the voting.  
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8f85c0e0-38c5-40bb-9471-76187af10317n%40googlegroups.com.

[sage-devel] Re: Modularization project: II. The tools

[Matthias Koeppe]

On Saturday, June 17, 2023 at 9:51:05 AM UTC-7 Matthias Koeppe wrote:

- #35790: Doctest # optional / # long / # needs annotation maintenance tool 



This is now ready for review.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/df485912-779e-439f-a3e9-239ec54b30d6n%40googlegroups.com.

[sage-devel] Re: Modularization project: II. The tools

[Matthias Koeppe]

On Saturday, June 17, 2023 at 9:51:05 AM UTC-7 Matthias Koeppe wrote:

Some new Issues / PRs to improve the tools:
 Codeblock-scoped # optional annotations for doctests (modularization) 
#35750 
#35790: Doctest # optional / # long / # needs annotation maintenance tool 



This is now implemented in https://github.com/sagemath/sage/pull/35749:
"Add style guide / reference for # optional - sage doctest tags, extend 
sage 
-t and sage -fixdoctests for modularization tasks"

Ready for review.
 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/826169f4-d987-4bc8-a9f2-2cb5f5077220n%40googlegroups.com.

[sage-devel] import gc; from sage.all import SR; fails on python 3.11 and sage 9.6

[Georgi Guninski]

On sage 9.6 and python 3.11:

>>> import gc
>>> from sage.all import SR
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib64/python3.11/site-packages/sage/all.py", line 127, in 
from sage.data_structures.all import *
  File "/usr/lib64/python3.11/site-packages/sage/data_structures/all.py",
line 2, in 
from .bitset import Bitset, FrozenBitset
  File "sage/data_structures/bitset.pyx", line 1, in init
sage.data_structures.bitset
ModuleNotFoundError: No module named 'memory_allocator'

This doesn't raise exception in sage shell.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGUWgD-z_VKPpgZYk64%2BgUECeRjzs4J4rTDDWDOpsU4-nW%3DSuw%40mail.gmail.com.