On 2015-09-12 09:48, Simon King wrote:
All versions from 2.1.2 till now were at least partially motivated by coping with backward incompatible changes.
I am probably responsible for several of these backward incompatible changes. However, they were changes to the basic Sage infrastructure, like moving of include directories, the removal of c_lib. Really, things which cannot be deprecated. And these changes were good changes, not just changes for the sake of changing stuff. For example, the inclusion of sage_include_directories() in sage.env should make the include directories future-proof.
And, as you mentioned, if an upstream package breaks things (for example Cython no longer allowing foo(mutable=True, mutable=True)), then there is not much that Sage can do.
Jeroen. -- 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.
