Ticket #8686 (closed defect: fixed)
gettext related bug in _ (history)
| Reported by: | logix | Owned by: | was |
|---|---|---|---|
| Priority: | minor | Milestone: | sage-4.5 |
| Component: | notebook | Keywords: | gettext history documentation |
| Cc: | was, timdumol | Work issues: | |
| Report Upstream: | N/A | Reviewers: | Tim Dumol |
| Authors: | Mike Hansen | Merged in: | SageNB 0.8.1 |
| Dependencies: | Stopgaps: |
Description
In versions of Sage up to 4.3.2, the following worked as expected:
>./sage ---------------------------------------------------------------------- | Sage Version 4.3.2, Release Date: 2010-02-06 | | Type notebook() for the GUI, and license() for information. | ---------------------------------------------------------------------- sage: _? [...] sage: _ '' sage: _ ''
However, with Sage 4.3.3, it has stopped working:
---------------------------------------------------------------------- | Sage Version 4.3.3, Release Date: 2010-02-21 | | Type notebook() for the GUI, and license() for information. | ---------------------------------------------------------------------- sage: _? [...] sage: _ '' sage: _ <bound method NullTranslations.ugettext of <gettext.NullTranslations instance at 0x4b1a680>>
For some things, the history works as expected, but for others it does not. To me it appears that it is "simple" things, e.g. above, the empty expression, or simple expressions like "3+4" where it does not work anymore, but for more complex things (e.g. if you call a function that returns something), "_" still does what you would expect it to do.
This bug still exists in Sage 4.3.5.
Attachments
Change History
comment:1 Changed 3 years ago by logix
- Owner changed from itolkov, jason to was
- Component changed from interact to user interface
- Authors Harold Gutch deleted
comment:2 Changed 3 years ago by mhansen
- Status changed from new to needs_review
- Authors set to Mike Hansen
comment:3 Changed 3 years ago by mhansen
- Cc was, timdumol added
- Component changed from user interface to notebook
Note: See
TracTickets for help on using
tickets.

