> Well, I think what we should do is merge as much of SPD into Sage as > possible to lessen the maintainance burden. One thing I could see here > is to define SAGE_EXECUTABLE and you would just set it to spd in your > code.
I think this is a good idea. I think if SPD is kept separate, it will end up being a lot of work for all of us. One case in point: I am about to submit some bug reports related to Sage and SPD. The bugs affect both and it seems silly to do double work and track/fix these issues in both places. But this brings up a question: Currently spd creates its own .spd directory for notebooks. Sage creates a .sage dir for its notebooks. We should probably keep these 2 separate (but also configurable) as the 2 get combined. Cheers, Brian --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
