#2031: serious preparser lameness involving time and comments
---------------------------+-----------------------------------------------
Reporter: was | Owner: was
Type: defect | Status: closed
Priority: major | Milestone: sage-duplicate/invalid/wontfix
Component: user | Resolution: invalid
interface | Merged in:
Keywords: | Reviewers:
Authors: | Work issues:
Report Upstream: N/A | Dependencies:
Branch: |
Stopgaps: |
---------------------------+-----------------------------------------------
Comment (by was):
Replying to [comment:4 mhansen]:
> {{{%time}}} is now handled by IPython and works with the comment lines.
We still have
>
> {{{
> sage: %time a = 2 + 2; a
> CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s
> Wall time: 0.00 s
> }}}
>
> but I think we can close this ticket.
My 2 cents. I wouldn't close this. This is in my opinion a bug in
Ipython now, but it is still a bug.
For comparison in a worksheet in https://cloud.sagemath.com, where I
implemented things from scratch (yet again), this works just fine:
{{{
INPUT: %time a = 2 + 2; a # or don't
OUTPUT: 4
CPU time: 0.00 s, Wall time: 0.00 s
}}}
It's bad for the behavior of a single line to depend on whether or not it
has %time in front of it. I don't know why IPython doesn't respect the
sys.displayhook though.
Perhaps this should be a new ticket though, and it should be reported
upstream to ipython. I.e., it's not longer a "Sage preparser" issue.
--
Ticket URL: <http://trac.sagemath.org/ticket/2031#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
