On Sun, 15 Jan 2023 at 12:26, Jason Moore <[email protected]> wrote: > > 1 year seems too short from my perspective. As a downstream package > maintainer, I release many packages less often than SymPy makes releases and > keeping up with deprecations disappearing effectively each SymPy release > would be stressful. I would advocate for at least 2 years, which equates to > at least a couple of SymPy releases. Or even stating something like > "deprecations can be removed if they've existed both for two years and two > SymPy releases".
To be clear the policy says "at least one year" i.e. that should be considered a minimum. I don't think that we should routinely remove deprecated features after only 1 year. Maybe 3 years is a better time frame for that. In some cases we should do it sooner but there should be some reason for doing it more quickly. > I also think the current method of leaving the deprecations in indefinitely > is fine and preferable. I don't think having a policy written in a way that > encourages people to constantly look for deprecations that are just over the > minimum time period to immediately remove them. They should really only be > removed when they both reach the minimum AND are causing some issue with new > code refactoring or designs. The point of deprecating things is so that they can eventually be removed or changed. Perhaps fewer things should be deprecated but saying that deprecated things should be left indefinitely defeats the purpose. -- Oscar -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAHVvXxRysLdxK%2BToPTP5%2Bn%2BesMTm50Qbd0Ufp-SUQSeRNC6QJw%40mail.gmail.com.
