Opened 11 years ago
Last modified 7 years ago
#8784 new defect
remove quit_sage() command from all.py top level
Reported by: | was | Owned by: | jason |
---|---|---|---|
Priority: | major | Milestone: | sage-6.4 |
Component: | misc | Keywords: | |
Cc: | Merged in: | ||
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
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.
wstein@boxen:~/build/sage-4.4$ ./sage ---------------------------------------------------------------------- | Sage Version 4.4, Release Date: 2010-04-24 | | Type notebook() for the GUI, and license() for information. | ---------------------------------------------------------------------- sage: quit_sage() Exiting Sage (CPU time 0m0.04s, Wall time 0m3.16s). sage: quit Exiting Sage (CPU time 0m0.07s, Wall time 0m4.80s). /virtual/scratch/wstein/build/sage-4.4/local/bin/sage-sage: line 206: 11559 Segmentation fault sage-ipython "$@" -i wstein@boxen:~/build/sage-4.4$
The fix is to rename quit_sage() somehow and change *all* code that calls it.
Change History (5)
comment:1 Changed 11 years ago by
comment:2 Changed 8 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:3 Changed 7 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:4 Changed 7 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:5 Changed 7 years ago by
- Milestone changed from sage-6.3 to sage-6.4
Note: See
TracTickets for help on using
tickets.
Maybe rename it to "sage_library_cleanup"?