Would something along the lines of http://www.lmfdb.org/ be what you're thinking of?
On Friday, February 19, 2016 at 4:48:11 PM UTC-5, Nathann Cohen wrote: > > Well, that's the "solve it by myself and for myself only". That's > always available, but I wondered if there was need for something more > general. > > Nathann > > On 19 February 2016 at 18:05, Travis Scrimshaw <tsc...@ucdavis.edu > <javascript:>> wrote: > > Hey Nathann, > > It seems like a good solution might be to maintain a small website > that > > holds this displays this information held in, say, a SQL database. Then > just > > add a link from the Sage documentation to this website. You could also > then > > write a small script to automatically update this on each (beta) version > of > > Sage. This approach could also make it more likely to be discoverable by > > other people too. > > > > Best, > > Travis > > > > > > On Friday, February 19, 2016 at 5:51:39 AM UTC-6, Nathann Cohen wrote: > >> > >> Hello everybody, > >> > >> Sage is able to produce a bunch of data that is rather interesting to > >> me. This data can change between different versions of Sage, and is (I > >> believe) of public interest. > >> > >> For this reason, I would like to publish [1] it online, and keep it up > >> to date with Sage. The easiest way would be for me to include it in > >> Sage's documentation [2], but: > >> > >> 1) Having it as a doctest is a bad idea, for this data can change > >> often and create a *lot* of branch conflicts while two persons work on > >> the code. > >> > >> 2) Having the module file add this data to the docstring means that > >> this computation would be performed every time the module is loaded. > >> > >> The data I have in mind is simply a 'list of numbers'. It could be > >> similar to this page [3], except that this data is hardcoded and thus > >> does not change often. The appearance would be the same, though: many > >> many numbers (in a more readable format), generated from Sage's own > >> databases. > >> > >> I write here to know if any of you would have similar needs. That may > >> also tell me how this should be implemented to fit everybody's needs. > >> > >> Thanks, > >> > >> Nathann > >> > >> [1] Not in the sense of a scientific publication. In the more common > >> sense of 'making public' > >> [2] See the big doctest at > >> > >> > http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/designs/latin_squares.html > > >> [3] > >> > http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/designs/database.html > > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "sage-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to sage-devel+...@googlegroups.com <javascript:>. > > To post to this group, send email to sage-...@googlegroups.com > <javascript:>. > > Visit this group at https://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
