Nick Alexander wrote: > May I suggest that sloane_functions be split into pieces, perhaps one > sequence per file? It takes for ever to run the tests, and it's > just... bulky. Too big. >
All tests passed! Total time for all tests: 10.5 seconds But you are right. There are 125k sequences in the OEIS, growing with a rate of ten to twenty a day, not all very interesting, but anyway. When sloane_functions.py grows with 10 sequences a day we will never catch up! You can cut down on doctesting, not on examples because of the educational impact. Users of the OEIS are probably occasional SAGE users, so examples and code inspection are important features. For the moment I think it is best to concentrate on sequences with the keywords 'core' and 'nice' (or 'hard'!). One sequence per file? There are groups of sequences built around a theme (recurrence, etc.), or depending on some other sequence. Will it be possible to group sequence > Also, do we envision the network code in databases/sloan eventually > being unified with the sloane_functions code? > This seems a good idea. For a sequence not implemented yet, switch to the Internet or the database to give some information: name, numbers and a link to the OEIS. Jaap --~--~---------~--~----~------------~-------~--~----~ 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-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
