If I set a deprecation now in 1.1dev then it the warning would operate in version 1.1.X and be removed for the 1.2 release. As you said.
But, most software packages seem to more-or-less let the first value of the version number indicate that there are backwards incompatible changes. So code written for SymPy 2.0 isn't guaranteed to work with SymPy 1.0 but code written for SymPy 2.10 that doesn't use features introduced since 2.0 should work for with versions 2.0-2.10. Our previous versioning had a leading 0 and we used four decimal places in the full version number, e.g. 0.7.4.1. It seems like the third value was changed when backwards incompatibilities were introduced and the fourth number was used for bug fixes and hot fixes. I guess I'm looking for clarity about what each of the four values in the version number represent. I'll reread the deprecation rules. Jason moorepants.info +01 530-601-9791 On Fri, Apr 1, 2016 at 8:37 AM, Aaron Meurer <asmeu...@gmail.com> wrote: > This is the current deprecation policy > https://github.com/sympy/sympy/wiki/Deprecating-policy. Perhaps some > of it needs to be updated for 1.0. > > The motivation for listing the first version in which it was > deprecated instead of the last is that we never came up with a > suitable policy for how long deprecations should last. The issue is > that the SymPy releases tend to be sparse. I haven't thought too hard > about how we'll version things going forward, or even how often we > will want to do releases. > > Anyway, if you're setting a warning now, that means the next version > will be at least 1.1, so wouldn't you not remove it until at least > 1.2? > > Aaron Meurer > > > On Fri, Apr 1, 2016 at 4:40 AM, Francesco Bonazzi > <franz.bona...@gmail.com> wrote: > > Maybe we should modify the deprecation decorator. Instead of pointing to > the first version in which the function has been deprecated, maybe point to > the last version in which it wasn't deprecated. > > > > -- > > 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 https://groups.google.com/group/sympy. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/12c4e72b-5a39-442d-a16b-0f796458f730%40googlegroups.com > . > > For more options, visit https://groups.google.com/d/optout. > > -- > 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 https://groups.google.com/group/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2B6zDxdvP3jbKqsSWYdwshVGUA94jSKeF_8bNGqQ9kWWQ%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAP7f1AiaBv5LSWZxKfJcB%3DYHL8NpKJBucpcm0_g%2B_ndxXmjd5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
