On Jan 20, 10:10 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Fri, 19 Jan 2007 22:17:00 -0800, Nick Alexander <[EMAIL PROTECTED]> 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.Yes. Do it. Put them in a subdirectory:
>
> sage/combinat/sloane/
>
> This will *not* helpw with running tests though -- it will take even longer!
> The solution for that is to not have any tests that take a long time. If
> they do, properly mark them with a comment
> sage: ... # long time
> so they don't get run by default.
What it does help is my dev cycle. I am in a loop:
edit file.py; sage -b && sage -t file.py
Building takes 5 seconds. Running the tests for sloane_functions.py
takes 50 seconds on my computer. That is a terribly long time to fix a
typo.
What I really need to do is update the doctesting architecture to make
it easier to test only certain things, but that is tricky in general.
> > Also, do we envision the network code in databases/sloan eventually
> > being unified with the sloane_functions code?Sure. Any proposals as to how?
I will think about it.
Nick
--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---
