#18941: Poset documentation polishing: chains and antichains
-------------------------------------+-------------------------------------
Reporter: jmantysalo | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.9
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Jori Mäntysalo | Reviewers: Kevin Dilks
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jmantysalo/poset_polishing_chains| ecb16e648cdff2cb22bc88c7fd01f114af8006a5
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ncohen):
> ? Or is there still something more to think about?
If you want to support any iterable as input, I guess that the best is
this
{{{
sage: elms = range(10)
sage: it1 = iter(elms)
sage: it2 = iter(elms)
sage: it2.next()
0
sage: zip(it1,it2)
[(0, 1), (1, 2), (2, 3), (3, 4), (4, 5), (5, 6), (6, 7), (7, 8), (8, 9)]
}}}
But that's really a lot of infrastructure for a very small impact.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18941#comment:29>
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.
