#17818: Interface to FindStat
-------------------------------------+-------------------------------------
       Reporter:  mantepse           |        Owner:
           Type:  enhancement        |       Status:  new
       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                          |  6caecea9f006c0b6637025685d9ebc5b992dbc5e
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by mantepse):

 I tried (with a lot of help from the FindStat team) to answer the
 (technical) objections raised above.  In case somebody is interested in
 having this finalized, I need a little help with the following items:

 1) documentation and doctests

 2) I believe that statistics, collections and maps should have something
 similar to a unique representation, but I'm not sure how to achieve this,
 especially for statistics.  I should mention that it is quite possible
 that at some point collections and maps can be edited, too.  So the idea
 is to have caching enabled for objects with id different from 0...

 3) Christian told me that I need to do something like lazy import, but I
 currently don't really know what that is.  I simply followed `oeis.py`...

 4) a design question: it appears that, in sage, python properties are
 hardly used at all.  I have no idea why.  Currently, the interface uses
 properties to allow editing statistics (collections and maps currently
 cannot be edited).  This implies some inconsistencies.  Therefore:

 - should I change read-only properties like `FindStatStatistic.id` to
 ordinary methods?
 - should I do the same with the other properties, i.e., provide methods
 `FindStatStatistic.description` and `FindStatStatistic.set_description`?

--
Ticket URL: <http://trac.sagemath.org/ticket/17818#comment:22>
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.

Reply via email to