> How often do you feel that changes in Sage breaks your code? Looking at my log (this project https://github.com/defeo/ss-isogeny-software)
- Sage 6.2: module renamed in Pari/GP interface (without deprecation, as far as I recall) - Sage 6.4: frankly, I don't know, but possibly a change in the finite fields implementation - Sage 6.7: changes in cython, not really Sage's fault, I guess - Sage 6.7: changes in the finite fields implementation (with proper deprecation, this time) - Sage 6.10: changes in richcmp (did not get deprecation warnings, but the change concerns an internal function) - Sage 7.1: affected by #19941 (properly deprecated, note that 7.1 is stable right now, but not yet in SMC) It may be argued that I'm taking risks because I sometimes fiddle with "the internals" of Sage, but one other problem of Sage is that it does not define clearly what's the public API and what's internal. Luca -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
