Hi, First of all, sorry for resurrecting this - I was browsing the issue page, there's one that references this thread and I felt making a new thread would lose us some context. Anyway, in working on Twisted (my GSoC for this year) - which is a much more structured project, with many development processes which must be kept - I got some ideas on this.
My proposal is to, for each deprecation warning, show the version it has been deprecated since and a link to the relevant issue (as Stefan proposed). The only new "rule" we would need is that each deprecation should have an issue (but I think they all do already and it is good practice anyway). This way, we can decide on each issue individually (eg. .is_real() is harmless and can stick around; piecewise() should probably be changed asap etc. -- this is what I understood Brian and Stefan wanted), we are not tied to any particular release schedule* and we give the user real information and a handy link for more. Code-wise, as far as I can see, SymPyDeprecationWarning has parameters to provide extra info (as requested in issue 2142 I guess[1]); these are currently "feature", "last_supported_version" and "useinstead". Per my proposal above, I would remove those three in favor of "since" and "ticket". I feel this would be more concise, and this information is easier to fit into a function decorator (in the sense that writing a long "useinstead" string is not very practical). Thoughts? [1] http://code.google.com/p/sympy/issues/detail?id=2142 * Which I think we should have anyway, but that's definitely a whole other thread; lets not discuss that here. -- You received this message because you are subscribed to the Google Groups "sympy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sympy/-/KyteWjHfyO0J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
