On Sat, Jan 1, 2011 at 6:09 PM, kcrisman <kcris...@gmail.com> wrote: > Happy New Year as well! > > Certainly sometimes we do simply remove methods which are used > absolutely nowhere in the code and are clearly for internal use only. > The way you describe this certainly make them seem like a candidate > for this.
I agree. Our deprecation policy (which is have a warning for at least one year), is generally a good idea. However, sometimes it should be skipped if it is very awkward to use. For some things, e.g., completely renaming a method, it makes perfect sense to leave the old one around for a year with a warning. Use common sense. -- William > > However, in general, we definitely are pretty careful with this, so > it's good to ask, since usually we would do the deprecation. But if > sage-algebra and/or sage-combinat feel you are justified, this *might* > be one of those cases (says the person who won't be using the category > framework). In theory, in 5.0 we are going to remove a whole bunch of > deprecated stuff... we'll see when that happens, though! > > - kcrisman > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- William Stein Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
