-
-
Notifications
You must be signed in to change notification settings - Fork 543
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Trac #33213: Replace SAGE_TMP by the system location in the sage library
Re: https://groups.google.com/g/sage-devel/c/zhjl_j6j_Qc These days, using a `SAGE_TMP` that by default lives under `$HOME` is overly complex and often inefficient. In this ticket we implement the first phase of its removal, to be replaced by python's `tempfile` module. Specifically, 1. We replace all direct uses of `SAGE_TMP` within the sage library and doctests. 2. We update `tmp_dir()` and `tmp_filename()` to use the `tempfile` defaults. 3. We remove `SAGE_TMP`. Afterward, the custom functions `tmp_dir()` and `tmp_filename()` can be deprecated in favor of `tempfile.TemporaryDirectory()` and `tempfile.NamedTemporaryFile()`. Moreover when #8784 is done, we'll be able to remove sage-cleaner entirely. URL: https://trac.sagemath.org/33213 Reported by: mjo Ticket author(s): Michael Orlitzky Reviewer(s): Matthias Koeppe, Dima Pasechnik
- Loading branch information
Showing
35 changed files
with
336 additions
and
255 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.