-
-
Notifications
You must be signed in to change notification settings - Fork 543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove quit_sage() command from all.py top level #8784
Comments
comment:1
Maybe rename it to "sage_library_cleanup"? |
Branch: u/mjo/ticket/8784 |
comment:6
Now all of the cleanup happens automatically and
New commits:
|
Commit: |
Author: Michael Orlitzky |
comment:8
Does this mean that |
comment:9
Replying to @dimpase:
Not yet, although that's another long-term goal of mine. sage-cleaner also cleans up "temporary" files, which it wouldn't have to do if we used the OS's built-in tempfile functions instead of our home-grown |
comment:11
OK, looks and tests good. |
Reviewer: Dima Pasechnik |
comment:12
perhaps you want to rebase on the latest beta |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. This was a forced push. New commits:
|
comment:14
oops, overlooked this, sorry. Looks good. |
Changed branch from u/mjo/ticket/8784 to |
Changed commit from |
comment:16
Follow up in #33706. |
comment:17
We have a complaint about ipython processes staying alive in a patchbot. Could it be due to this ticket, perhaps the change for |
It is stupid that it is this easy to accidentally destabilize and segfault Sage. Also, having a function "quit_sage()" available at the sage: prompt by default that does not quit sage, is dumb.
The fix is to rename quit_sage() somehow and change all code that calls it.
Component: misc
Author: Michael Orlitzky
Branch:
ef89f43
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/8784
The text was updated successfully, but these errors were encountered: