[sage-devel] Re: Temporary files problems

[Andrey Novoseltsev]

I think it must be customizable, and also its use should be checked for 
errors - if it does not exist anymore, it should be recreated... Public 
SageCell servers probably see enough traffic to keep it alive, but people 
with private servers are very likely to run into problems, e.g. when their 
students are sleeping or pub crawling, all at once ;-)

-- 
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/53ebd0ef-dd25-4324-b2fd-0b44a478c577n%40googlegroups.com.

[sage-devel] Re: Temporary files problems

[John H Palmieri]

See also 
https://ask.sagemath.org/question/64192/temporary-html-files-location-in-sage-97/
 
— some browsers can't access local files in /tmp from the notebook, so 
plots do not appear. Perhaps TMP_DIR_FILENAME_BASE could be customizable. 
Other options?

On Monday, September 26, 2022 at 7:58:01 PM UTC-7 novo...@gmail.com wrote:

> Hello!
>
> I've run into this while testing upgrades to Ubuntu 22.04 from 20.04, but 
> it seems that it comes from how temporary files are handled in Sage 9.7:
>
> TMP_DIR_FILENAME_BASE=tempfile.TemporaryDirectory()
>
> this temporary directory is created and then used ever after. But what if 
> it gets deleted? For example, what if someone uses tmpreaper or something 
> similar, when old files are removed from /tmp? Sage does not notice it, but 
> things break in a weird way, e.g. plots are not displayed and the error 
> message is not transparent.
>
> I believe this is exactly what is happening and I would appreciate some 
> attention to this matter ;-)
>
> Thank you!
> Andrey
>

-- 
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/77b4298e-9810-4432-8e4c-22d1934be009n%40googlegroups.com.

[sage-devel] Temporary files problems

[Andrey Novoseltsev]

Hello!

I've run into this while testing upgrades to Ubuntu 22.04 from 20.04, but 
it seems that it comes from how temporary files are handled in Sage 9.7:

TMP_DIR_FILENAME_BASE=tempfile.TemporaryDirectory()

this temporary directory is created and then used ever after. But what if 
it gets deleted? For example, what if someone uses tmpreaper or something 
similar, when old files are removed from /tmp? Sage does not notice it, but 
things break in a weird way, e.g. plots are not displayed and the error 
message is not transparent.

I believe this is exactly what is happening and I would appreciate some 
attention to this matter ;-)

Thank you!
Andrey

-- 
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/5ee63ec7-26b2-4c32-a5a7-45fb63a11327n%40googlegroups.com.

Re: [sage-devel] Re: VOTE: move Sage development to Github

[Andrey Novoseltsev]

+1 for Github

-- 
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/c259f261-dc79-4d93-8fe2-fad5f977de54n%40googlegroups.com.

[sage-devel] Re: Please add your GitHub account name to the SageMath contributor info

[Matthias Koeppe]

Hi all:
If you haven't had a chance to update your info: there's still time until 
October 5. Thanks!

On Monday, September 12, 2022 at 5:12:33 AM UTC-7 Matthias Koeppe wrote:

> Dear Sage developers (current and past):
>
> The SageMath developer map (https://www.sagemath.org/development-map.html) 
> needs your updated information.
>
> In particular, motivated by the proposed migration from Trac to GitHub 
> Issues/PRs (https://trac.sagemath.org/ticket/30363), we will need your 
> GitHub account name by September 26.
> (If you don't have a GitHub account yet, now is a great time to open one.)
>
> The source code of the Sage website is maintained in the GitHub repository 
> https://github.com/sagemath/website; to add yourself or to update your 
> information shown in the development map, edit the file 
> https://github.com/sagemath/website/blob/master/conf/contributors.xml and 
> send a pull request (PR). 
> - For your GitHub user name, use the "github" attribute.
> - For your (legacy) Trac user name, use the "trac" attribute. If you 
> already use a GitHub login for Trac, i.e., your Trac user name starts with 
> "gh-", there is no need to add the "trac" attribute.
> - If you have a Gitlab.com account, you can also add that if you want, 
> using the "gitlab" attribute.
>
> You can do all of this editing directly on GitHub by clicking the "Edit" 
> button; or, if you prefer, you can fork the repository, clone it to your 
> computer, edit it there, commit the change, push it to your fork, and send 
> a PR.
>
> We would also like to consolidate the Sage developer map information with 
> the information currently at 
> https://trac.sagemath.org/#AccountNamesMappedtoRealNames; if your name 
> appears on this Trac page, please help us by doing the following:
> - review the information there, move it to the contributors.xml file, and 
> then delete it from the Trac page.
>
>
>
>

-- 
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/8af50ce5-379a-443a-bc33-11652c034193n%40googlegroups.com.

[sage-devel] Re: make error

[Matthias Koeppe]

Yes, the compiler is too old. 
configure:5271: checking for C compiler version configure:5280: gcc 
--version >&5 gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44) 

Check if there's a better compiler available on this system. 
https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8#SupportforGCC8droppedC17featuresnowavailable

On Monday, September 26, 2022 at 5:53:26 PM UTC-7 guoha...@tamu.edu wrote:

> Hello,
>
> I have problems building sage with "make". I use a Linux machine. The 
> attachments are the log file. Is it because the gcc version on my machine 
> is not compatible with sage? Or any ideas? Thanks in advance!
>
> Regards,
> Hao
>

-- 
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/62e362d2-9535-4641-b93c-0fd16da39f58n%40googlegroups.com.

[sage-devel] Python 3 iterators on dictionaries

[Nils Bruin]

While Python 3 has stricter checks on iterators on dictionaries, they can 
still produce poorly defined, unexpected results without an error being 
raised: the only check is that any time an element is fetched, the length 
of the dictionary equals the length it had when the iterator was created. 
If entries are only changed (not added or deleted), iteration is pretty 
well-defined: you'll see every key once.

However, if a lot of keys are deleted and then recreated, a reshaping of 
the dictionary may still be triggered and then results on the returned keys 
are quite hard to predict. Example:

W = dict(enumerate(range(2000)))
I = iter(W) 
K = []

# fetch some elements from the iterator
for i in range(20): K.append(next(I))

# delete half of the entries
for i in range(0, 2000, 2): del W[i]

# and put other ones back
for i in range(0, 2000, 2): W[i]=i

#and fetch the rest of the iterator   
for i in range(20, 2000): K.append(next(I))

21 in K  # this is false
21 in W  # this is true

# so, we've never seen key 21. Obviously, there are other keys we've seen 
multiple times now.

# and we check the iterator is done:
next(I)  # raises StopIteration

-- 
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/bf850faa-7359-4d6a-98e9-82ce12c120e4n%40googlegroups.com.

[sage-devel] Re: Invitation: Weekly 30-minute Sage developer calls on Jitsi

[Matthias Koeppe]

Many thanks to all who joined the call today!
I've 
updated https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b 
according to our discussions regarding the details of the proposed 
migration to GitHub.

On Monday, September 26, 2022 at 10:01:16 AM UTC-7 Matthias Koeppe wrote:

> Reminder: This is today ---
> Monday morning, 11:15am San Francisco
> Monday afternoon, 2:15pm New York
> Monday evening, 20:15 Paris
> https://meet.jit.si/VibrantTribesBearEver 
> 
>
>
> On Monday, September 19, 2022 at 9:02:39 PM UTC-7 Matthias Koeppe wrote:
>
>> Dear all,
>> Our first Sage developer calls last Thursday/Friday on Zoom were very 
>> successful! 
>>
>> We are switching to video conferencing on Jitsi from now on. It is open 
>> source software; see https://jitsi.org/about/
>>
>> Thanks to all who filled out the poll to find times for regular meetings. 
>> We'll use the following weekly schedule from now on. (The poll is still 
>> open -- we can periodically readjust according to people's changing 
>> availability – http://whenisgood.net/2kbimt4)
>>
>> Call A:
>> Thursday evening, 9:15pm Oakland (California)
>> Friday afternoon, 4:15pm Auckland (New Zealand)
>> Friday early afternoon, 13:15 Tokyo
>> https://meet.jit.si/WellMixesPictureThere 
>> 
>>
>> Call B:
>> Monday morning, 11:15am San Francisco
>> Monday afternoon, 2:15pm New York
>> Monday evening, 20:15 Paris
>> https://meet.jit.si/VibrantTribesBearEver 
>> 
>>
>> You can put these meetings on your calendar by subscribing to this Google 
>> calendar:
>>
>> https://calendar.google.com/calendar/u/0?cid=YXI3bzc4ZXE3bW42NWd2dnZwajVtOGc5NGNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
>>
>> (Organizers of other Sage activities around the world: Contact me if you 
>> wish to put your activities on the calendar.)
>>
>>
>>
>>

-- 
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/546d3fec-a885-4aa2-b52b-2a489d27dde4n%40googlegroups.com.

[sage-devel] Re: Invitation: Weekly 30-minute Sage developer calls on Jitsi

[Matthias Koeppe]

Reminder: This is today ---
Monday morning, 11:15am San Francisco
Monday afternoon, 2:15pm New York
Monday evening, 20:15 Paris
https://meet.jit.si/VibrantTribesBearEver 



On Monday, September 19, 2022 at 9:02:39 PM UTC-7 Matthias Koeppe wrote:

> Dear all,
> Our first Sage developer calls last Thursday/Friday on Zoom were very 
> successful! 
>
> We are switching to video conferencing on Jitsi from now on. It is open 
> source software; see https://jitsi.org/about/
>
> Thanks to all who filled out the poll to find times for regular meetings. 
> We'll use the following weekly schedule from now on. (The poll is still 
> open -- we can periodically readjust according to people's changing 
> availability – http://whenisgood.net/2kbimt4)
>
> Call A:
> Thursday evening, 9:15pm Oakland (California)
> Friday afternoon, 4:15pm Auckland (New Zealand)
> Friday early afternoon, 13:15 Tokyo
> https://meet.jit.si/WellMixesPictureThere 
> 
>
> Call B:
> Monday morning, 11:15am San Francisco
> Monday afternoon, 2:15pm New York
> Monday evening, 20:15 Paris
> https://meet.jit.si/VibrantTribesBearEver 
> 
>
> You can put these meetings on your calendar by subscribing to this Google 
> calendar:
>
> https://calendar.google.com/calendar/u/0?cid=YXI3bzc4ZXE3bW42NWd2dnZwajVtOGc5NGNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
>
> (Organizers of other Sage activities around the world: Contact me if you 
> wish to put your activities on the calendar.)
>
>
>
>

-- 
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/304ba28a-aeb2-461b-a8fd-3496ad2bf6a8n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Matthias Koeppe]

On Monday, September 26, 2022 at 1:35:04 AM UTC-7 Eric Gourgoulhon wrote:

>  
>
>> How long do we want to have Trac still exist, but be read-only? 
>>  Obviously we wouldn't take it down right away, but presumably eventually 
>> we would need to do so.  
>>
>
> As I said earlier, discussions on Trac constitute a very valuable database 
> for Sage development. As far as I am concerned, I learned a lot from them. 
> It would be a pity to lose them.
>

Yes, of course, that's why the plan is to convert all tickets to Issues! 
That includes all closed tickets and all comments on the tickets.
Preview of converted tickets: https://github.com/sagemath/trac_to_gh/issues
 

-- 
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/85538f7a-91d1-4059-9b92-a36bfa9c33cbn%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Dima Pasechnik]

On Mon, Sep 26, 2022 at 10:26 AM Tobias Diez  wrote:
>
>
>
>> 2. Convert all tickets to Issues in a new repo. (This preserves the ticket 
>> numbers as Issue numbers.)
>
>
> Would it make sense to convert tickets with branches directly to 
> pull-requests?

only open tickets.
Closed tickets are served well enough by changing links to branches on
sagetrac-mirror.

>  Since most of them probably already contain quite a bit of discussion about 
> the implementation, which you would like to have as a easy reference if you 
> would review the PR later.
>
>>
>> 4. Replace sagemath/sage by the new repo.
>
>
>  If you rename a repo (in our case sage -> sage-old), then github adds 
> redirects for issues etc in sage to sage_old. So it should be double-checked 
> that you can later indeed add a new repo with the name sage.
>
> --
> 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/6418ac37-a858-447a-be9f-f7d7f4da9461n%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/CAAWYfq31AH0uPEBpqPOSOtuidD2TdmrNe%3D%2BQE1ow68wMuH%3Dyyw%40mail.gmail.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Tobias Diez]

2. Convert all tickets to Issues in a new repo. (This preserves the ticket 
> numbers as Issue numbers.)
>

Would it make sense to convert tickets with branches directly to 
pull-requests? Since most of them probably already contain quite a bit of 
discussion about the implementation, which you would like to have as a easy 
reference if you would review the PR later. 
 

> 4. Replace sagemath/sage by the new repo.
>

 If you rename a repo (in our case sage -> sage-old), then github adds 
redirects for issues etc in sage to sage_old. So it should be 
double-checked that you can later indeed add a new repo with the name 
sage.  

-- 
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/6418ac37-a858-447a-be9f-f7d7f4da9461n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Eric Gourgoulhon]

Le samedi 24 septembre 2022 à 13:57:36 UTC+2, kcrisman a écrit :

>
> On another note, I realize that the comment I made 6 years ago after 
> Volker's comment is still relevant:  
> "There's also the non-trivial (though not blocker, probably) issue that 
> zillions of links to trac.sagemath.org would instantly be obsolete"
>
>
This is a good point IMHO. In particular, there are zillions of links to 
Trac from the sage-devel threads.
 

> How long do we want to have Trac still exist, but be read-only?  Obviously 
> we wouldn't take it down right away, but presumably eventually we would 
> need to do so.  
>

As I said earlier, discussions on Trac constitute a very valuable database 
for Sage development. As far as I am concerned, I learned a lot from them. 
It would be a pity to lose them. 

Eric. 

-- 
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/e6bac55f-8cd2-4bcd-9308-d411a34d5eben%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Kwankyu Lee]

On Monday, September 26, 2022 at 3:17:03 PM UTC+9 Kwankyu Lee wrote:

> On Monday, September 26, 2022 at 12:21:41 PM UTC+9 John H Palmieri wrote:
>
>> Is there a vision for what Sage 10.0 means?
>
>
 Yes. See the headline of 

https://trac.sagemath.org/ticket/29705

-- 
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/241796ef-94a6-4bdd-b4a7-500460e9496dn%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Kwankyu Lee]

On Monday, September 26, 2022 at 12:21:41 PM UTC+9 John H Palmieri wrote:

> Is there a vision for what Sage 10.0 means?


Sage 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/aa5f330a-60cd-4657-92af-0ee438fc98e9n%40googlegroups.com.