#10358: The sloane_find command is now completely broken
---------------------------+------------------------------------------------
Reporter: was | Owner: tmonteil
Type: defect | Status: needs_work
Priority: critical | Milestone: sage-4.6.2
Component: combinatorics | Resolution: duplicate
Keywords: | Author:
Upstream: N/A | Reviewer:
Merged: | Work_issues:
---------------------------+------------------------------------------------
Comment(by nthiery):
Salut Thierry,
Rather than having a bunch of functions to return the various pieces of a
Sloane result, there could be a single object from which one could query
the pieces via methods. Something like:
{{{
sage: s = sloane_find([1,1,2,5,8,14])[0]
sage: s.description()
...
sage: s[6]
42
}}}
Actually, Anders Claesson [1] had implemented a prototype of this feature
during FPSAC'09, and his demo was quite cool. I guess he would agree to
give his code away for someone else to finalize it and merge it into Sage.
But maybe that should be the topic of a separate ticket.
[1] http://combinatorics.is/anders/
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10358#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
