Opened 12 years ago
Closed 2 years ago
#9688 closed defect (invalid)
sage notebook: Output of sh.eval? is corrupted
Reported by: | William Stein | Owned by: | jason, was |
---|---|---|---|
Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
Component: | notebook | Keywords: | |
Cc: | Frédéric Chapoton | Merged in: | |
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
Try doing
sh.eval?
in the Sage notebook, and the output gets corrupted, because the example in the docstring is complicated.
Change History (6)
comment:1 Changed 9 years ago by
Milestone: | sage-5.11 → sage-5.12 |
---|
comment:2 Changed 9 years ago by
Milestone: | sage-6.1 → sage-6.2 |
---|
comment:3 Changed 8 years ago by
Milestone: | sage-6.2 → sage-6.3 |
---|
comment:4 Changed 8 years ago by
Milestone: | sage-6.3 → sage-6.4 |
---|
comment:5 Changed 2 years ago by
Cc: | Frédéric Chapoton added |
---|---|
Milestone: | sage-6.4 → sage-duplicate/invalid/wontfix |
Status: | new → needs_review |
comment:6 Changed 2 years ago by
Resolution: | → invalid |
---|---|
Status: | needs_review → closed |
Note: See
TracTickets for help on using
tickets.
Proposing to close all sagenb tickets as outdated, so that all remaining open tickets in the notebook component are about the Jupyter notebook.