#17378: Preparser gets lost with iterated ellipsis_range
-------------------------------------+-------------------------------------
Reporter: tmonteil | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.5
Component: user interface | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/nbruin/preparser_gets_lost_with_iterated_ellipsis_range|
0c0ddd9935c9907906c7627e9d20538f443c6b23
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by nbruin):
* commit: => 0c0ddd9935c9907906c7627e9d20538f443c6b23
Comment:
OK, I did not deal with the extra comma replacements (which seem
relatively harmless). i think the "..." detection is simply a matter that
those "..." can be replaced by `Ellipsis` but should not trigger the
generation of an `ellipsis_range`/`ellipsis_iter`. That's my current
interpretation.
----
New commits:
||[http://git.sagemath.org/sage.git/commit/?id=0c0ddd9935c9907906c7627e9d20538f443c6b23
0c0ddd9]||{{{trac 17378: make sure preparse_ellipsis deals with nested
ranges properly}}}||
--
Ticket URL: <http://trac.sagemath.org/ticket/17378#comment:4>
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/d/optout.
