On Tuesday, September 27, 2022 at 10:11:00 AM UTC-7 dim...@gmail.com wrote:

> Basically, we should deprecate and remove tmp_dir() and tmp_filename() 
> from Sage. 
> Does Sagecell use them? It should not, Python3 has perfectly good 
> replacements... 
>

As long as we test everything on a variety of platforms and browsers, 
because it seems that things are broken on some platforms now. 
https://ask.sagemath.org/question/64192/temporary-html-files-location-in-sage-97/

 

>
> On Tue, Sep 27, 2022 at 6:06 PM Matthias Koeppe 
> <matthia...@gmail.com> wrote: 
> > 
> > Previous discussion -- in the ticket that made these changes to SAGE_TMP 
> --- https://trac.sagemath.org/ticket/33213#comment:11 
> > 
> > 
> > On Tuesday, September 27, 2022 at 9:10:28 AM UTC-7 novo...@gmail.com 
> wrote: 
> >> 
> >> On Tuesday, 27 September 2022 at 03:22:47 UTC-6 dim...@gmail.com 
> wrote: 
> >>> 
> >>> On Tue, Sep 27, 2022 at 3:58 AM Andrey Novoseltsev <novo...@gmail.com> 
> wrote: 
> >>> > this temporary directory is created and then used ever after. But 
> what if it gets deleted? 
> >>> I think it's meant to be used in a context manager, i.e. with with 
> >>> statement, e.g., citing python docs: 
> >>> 
> >>> >>> with tempfile.TemporaryDirectory() as tmpdirname: 
> >>> ... print('created temporary directory', tmpdirname) 
> >>> >>> 
> >>> # directory and contents have been removed 
> >>> 
> >>> Or with a callback (from Sage source) 
> >>> 
> >>> TMP_DIR_FILENAME_BASE=tempfile.TemporaryDirectory() 
> >>> atexit.register(lambda: TMP_DIR_FILENAME_BASE.cleanup()) 
> >>> 
> >>> 
> >>> Needless to say, one can interfere with it in a bad way messing around 
> >>> with ~/.sage/ - but so it the case for any file-based process... 
> >>> 
> >> 
> >> It seems to me like a pretty common and sensible practice, that /tmp 
> directories get cleaned up, especially on systems with lots of activity. I 
> would not consider it as "a bad way messing around". But creating a 
> temporary directory and then counting on it being there hours later for 
> another quick temporary operation may be a bit too optimistic. That 
> callback is designed to clean up after Sage quits, which is a good thing to 
> do, but it is not related to being able to use the directory. 
> > 
> > -- 
> > 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+...@googlegroups.com. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/8400b398-f51a-4a1b-a911-32f60ef8b8fdn%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/86132f9c-85ef-4d16-a699-0625795371f8n%40googlegroups.com.

Reply via email to