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:

Status badges

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 Jeroen Demeyer

Milestone: sage-5.11sage-5.12

comment:2 Changed 9 years ago by For batch modifications

Milestone: sage-6.1sage-6.2

comment:3 Changed 8 years ago by For batch modifications

Milestone: sage-6.2sage-6.3

comment:4 Changed 8 years ago by For batch modifications

Milestone: sage-6.3sage-6.4

comment:5 Changed 2 years ago by Matthias Köppe

Cc: Frédéric Chapoton added
Milestone: sage-6.4sage-duplicate/invalid/wontfix
Status: newneeds_review

Proposing to close all sagenb tickets as outdated, so that all remaining open tickets in the notebook component are about the Jupyter notebook.

comment:6 Changed 2 years ago by Frédéric Chapoton

Resolution: invalid
Status: needs_reviewclosed
Note: See TracTickets for help on using tickets.