The deprecation warning should include the Sage version where it was
deprecated, as in
deprecation('foobar is deprecated', 'Sage Version 4.8')
On Sunday, June 10, 2012 5:23:36 PM UTC+1, John Cremona wrote:
>
> We have a rule about giving a deprecation output warning when the user
> interface of a function changes, and somewhere is written down how
> long that should remain in place. But is there an easy way to tell?
>
> I tried using "hg blame" which tagged the lines I was looking at with
> the number 12039, but that does not refer to a relevant trac ticket.
> I put the number into the search box at
> http://hg.sagemath.org/sage-main and miraculously the first hit led me
> to changeset 12039:b9efad4a61dd, dated Fri Apr 03 16:29:44 2009 -0700
> (3 years ago) -- which is not the right one, looks like a reviewer's
> patch -- and the second hit seems to be the one I was looking for
> (same date).
>
> Perhaps it would make life simpler if whenever people write code
> introducing a new deprecation warning, there's a date? Though the
> time of writing the code and the date of the release can be years
> apart, so what then?
>
> In the case I was looking at (for ticket #13100) I think I am sage in
> removing the deprecation messages, and my patch there will do so.
>
> John
>
--
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
