> The current policy of 1 year + major release seems reasonable to me in > practice. It might make sense to lengthen that in a few years though. >
Yeah, this seems okay to me at this point, even though I know I usually argue for longer and longer. Part of my practical concern is that, from the standpoint of educators at institutions which need to use Sage because they can't afford the proprietary alternatives, we often do not have the resources to teach the same thing every semester, or even every year, so 1.5 years later might really be the next time I look at worksheet X (unless I want to waste a lot of valuable time in between checking out old worksheets with every Sage release). Is it possible for there to be something like sage -t, but which one could just run on a worksheet directory and would check for DeprecationWarnings or something? It would be really nice to do sage -tw .sage_notebook and it would automatically test all the text files to make sure they actually run - not necessarily that they get the same results as in the worksheets, since sometimes one saves a change in the Sage cell without evaluating it. This is a very half-baked idea, but it just popped in my mind as a big time saver, esp. if it was promoted properly with the notebook, maybe even a clickable thing from the home index page. And it would be a lot easier than opening 30 or 40 worksheets at the beginning of a semester and scrambling to fix things. - kcrisman --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
