#17818: Interface to FindStat
-------------------------------------+-------------------------------------
Reporter: mantepse | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.6
Component: interfaces | Resolution:
Keywords: FindStat | Merged in:
Authors: Martin Rubey | Reviewers:
Report Upstream: N/A | Work issues:
Branch: public/findstat- | Commit:
interface | d604a77e06fda46c4f560ee267a033eda1672855
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by stumpc5):
Replying to [comment:46 mantepse]:
> Well, but if this doctest (as currently written) doesn't pass, the
interface will not work reliably: user might get a result where her
statistic is produced via a map from a statistic on the new collection.
I am not necessarily arguing about doctest that tests whether the
interface still works well (even though my general concern also applies to
those, and e.g. the OEIS interface was broken several times IIRC).
What about the doctest
{{{
sage: print findstat(1).description() # optional -- internet
The number of ways to write a permutation as a minimal length product of
simple transpositions.
}}}
after someone has changed the description of this statistic? Or the case
that we added another collection -- would that break the interface, or
would it only not serve the new collection as long as it is not added?
--
Ticket URL: <http://trac.sagemath.org/ticket/17818#comment:48>
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.
