#17219: Automatically built catalogs
-------------------------------+------------------------
       Reporter:  nthiery      |        Owner:
           Type:  enhancement  |       Status:  new
       Priority:  major        |    Milestone:  sage-6.4
      Component:  categories   |   Resolution:
       Keywords:               |    Merged in:
        Authors:               |    Reviewers:
Report Upstream:  N/A          |  Work issues:
         Branch:               |       Commit:
   Dependencies:               |     Stopgaps:
-------------------------------+------------------------

Comment (by nthiery):

 Replying to [comment:3 ncohen]:
 > Automatically built catalogs "for algebraic structures". You will not
 make this work with hypergraphs.<tab>, designs nor graphs/digraphs, there
 are no categories nor testsuites there.

 Well, arguably there should be TestSuite's for graphs and friends :-)
 Other than that, it should be easy to let the infrastructure also
 gather data for certain abstract classes (e.g. GenericGraph) in
 addition to categories.

 That being said if the current workflow for building and maintaining
 the catalogs for graphs and friends is deemed good enough, we don't
 have to change it!

 > By the way there is a thing that I do not understand: do you
 > actually intend to make the doctests, though the calls to testsuite,
 > actually fill Sage's database of catalogs ? Does that mean that the
 > doctests will actually have an effect on the code ?
 >
 > Or is it only to detect that the catalog already contains what is
 > expected to be present ?

 Well, I sure would not want every user to have to run the tests to
 have a full featured Sage :-)

 So I am thinking of a two stage process, like for the pickle database:

 - When Sage would be put in a certain mode, TestSuite would be
   instrumented to gather the data and fill up the database needed for
   the automatic catalogs. This could typically be done as an
   additional step of the release process. Of course this needs to be
   automatized to not add burden to the release manager; and the
   specifics of this need to be settled.

 - This database would be shipped with the Sage distribution, be it in
   source or binary form, typically as an spkg or something similar.

 Cheers,
                                         Nicolas

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