Am 20.10.2014 um 00:48 schrieb Aaron Meurer:
[SymPy] definitely should support subclassing.
In that case, the pattern should be that SymPy code should avoid calling deprecated functions, except for the one function that replaces the deprecated one, which *must* call the deprecated one so that code that overrides the deprecated function will continue to work.
It's not always possible to do it that way, of course (e.g. if some functionality is simply being removed).
However, "do not call deprecated stuff from SymPy at all" isn't a viable guideline, you need to list the cases where it's actually okay to do so.
A short, potentially nonexhaustive list: - Calls from deprecated to deprecated code. - Old code is being superseded by new code, new code implements its functionality by calling old code. Removal of deprecated function usually means that you inline the deprecated function. - If we wish to keep subclasses functional without forcing them to override the new, non-deprecated functions as well. HTH -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/5446272B.9090509%40durchholz.org. For more options, visit https://groups.google.com/d/optout.
