> >> Of course, when writing code, we have no idea what date the next
> >> release
> >> would be, and sometimes are mistaken about the release that the patch
> >> will be included in as well. How should we take care of this
> >> patch-updating problem?
> >
> > I've been lazy to raise this problem on the lists. Sorry for that.
> >
> > Is this really a problem a warning tells that a function is
> > deprecated since
> > version 3.1 whereas it was really deprecated in version 3.2 ? If
> > yes a
> > possible solution is the following:
>
> It's deprecated as soon as a decision is made.
So should I understand that you even don't want to mention any sage version in
the deprecation warning. IE you'd rather have
sage: Partition([2,1]).boxes()
DeprecationWarning: (Since 2009-09-10) The function bar is removed.
Than
sage: Partition([2,1]).boxes()
DeprecationWarning: (Since Sage Version 4.2, Release Date: 2009-10-24) boxes is
deprecated. Please use cells instead.
> > Add in the file version.py a dictionary which contains all the
> > previously
> > released version:
> >
> > past_release_date = {
> > "4.1" : '4395-08-23',
> > "4.2" ...
> > }
>
> Or use the revision control to automatically find the date for any
> given release.
Thats makes sense... (Though I have to learn how to do it from inside sage :-)
Cheers,
Florent
--
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
