Deprecation works in the Sage library because it is being tested. Nobody can test optional spkgs against a wide range of past and future Sage versions. And not tested = does not work.
Case in point, no Linux distribution makes any promises that packages from other versions of their distribution work. They might, but then they might not. And often they don't. By coupling spkg install scripts closer to the sage library we can actually test that the optional spkg installs, or at least installs on some platform, or at least doesn't fail because of a trivial change in the Sage directory layout. Imho thats the proper solution, and not propping an untested deprecation framework and an untested dependency framework on top of the spkg system. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. 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. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
