#3986 closed defect (invalid)
notebook -- a doc browser bug
| Reported by: | was | Owned by: | boothby |
|---|---|---|---|
| Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
| Component: | notebook | Keywords: | |
| Cc: | Merged in: | ||
| Authors: | Reviewers: | ||
| Report Upstream: | N/A | Work issues: | Still a problem? |
| Branch: | Commit: | ||
| Dependencies: | Stopgaps: |
Status badges
Description (last modified by )
- Go to any interactive help sheet in the notebook.
- Go the very very bottom cell, below the text.
- Press shift enter.
- I get this traceback in the server log:
... cell.evaluate(username = self.username) exceptions.AttributeError: TextCell instance has no attribute 'evaluate'
It's bad form getting tracebacks in the server log, though everything continues to work fine. The fix is to figure out why a text cell is having evaluate called on it. Is the bottom cell somehow incorrectly set to be a text cell?
Change History (5)
comment:1 Changed 12 years ago by
comment:2 Changed 11 years ago by
- Status changed from new to needs_info
- Work issues set to Still a problem?
comment:3 Changed 11 years ago by
- Report Upstream set to N/A
- Resolution set to invalid
- Status changed from needs_info to closed
This doesn't seem to be a problem in sagenb-0.6.
comment:4 Changed 11 years ago by
- Milestone changed from sage-4.3.1 to sage-duplicate/invalid/wontfix
comment:5 Changed 6 years ago by
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
Is this still a problem?