On Saturday, September 12, 2015 at 9:48:38 AM UTC+2, Simon King wrote: > > For the record: I think ANY backward incompatible internal change that > *can* > be covered by a deprecation warning (thus, changed import locations, > changed function names or argspecs, etc) *has* to be covered by a > deprecation period
Thats madness, this means that we cannot change anything in Sage at all because surely somebody imported that private function somewhere. If its not globally exported (i.e. you can't import it from sage.all) then there is no guarantee of stability. I dare you find any project that makes stability guarantees for non-public APIs. I wonder why nobody else does it... > I thought some patchbots did test optional packages on a more or less > regular > basis? > No, the build/patchbots only test standard packages. Of course we would be happy to have you volunteer as the person in change of testing all optional packages. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
