Re: [sage-devel] Moving SAGE_TMP to the system location

2022-02-15 Thread Michael Orlitzky
On Sun, 2022-02-13 at 09:57 -0500, Michael Orlitzky wrote: > > If not, I'm proposing we, > > 1. Replace all direct uses of SAGE_TMP in library/doctest code with  > python's tempfile module. > 2. Drop SAGE_TMP from tmp_filename() and tmp_dir(); this will revert > to whatever director

Re: [sage-devel] Moving SAGE_TMP to the system location

2022-02-13 Thread François Bissey
> On 14/02/2022, at 03:57, Michael Orlitzky wrote: > > If not, I'm proposing we, > > 1. Replace all direct uses of SAGE_TMP in library/doctest code with > python's tempfile module. > 2. Drop SAGE_TMP from tmp_filename() and tmp_dir(); this will revert > to whatever directory the OS

Re: [sage-devel] Moving SAGE_TMP to the system location

2022-02-13 Thread William Stein
On Sun, Feb 13, 2022 at 6:57 AM Michael Orlitzky wrote: > > tl;dr I think we should forego SAGE_TMP and use whatever the system's > temporary location is. +1. I'm pretty sure I "created" this SAGE_TMP thing in the first place, and that my reasons were: a. ignorance about the built in Python sol

[sage-devel] Moving SAGE_TMP to the system location

2022-02-13 Thread Michael Orlitzky
tl;dr I think we should forego SAGE_TMP and use whatever the system's temporary location is. The first-order benefits of that are, 1. No need to maintain SAGE_TMP code ourselves. 2. The system temporary location is often optimized for temporary  access (e.g. is mounted in RAM), and is a