On 6/11/12 10:02 AM, William Stein wrote:
I guess the new trac_number field will have to default to None, unless
we want to raise a deprecation warning whenever deprecation() is only
called with two arguments...infiinte loop?!
I count about 132 times where deprecation is imported and about 70
times where deprecation() is called. Roughly.
I would just suggest:
deprecation(msg,trac_number)
where both arguments are mandatory. Once this code is in Sage, one
can deduce every possible thing discussed above in this thread from
the trac number. The deprecation warning can produce the URL of the
trac ticket. In my opinion this (Volker's suggestion) is a brilliant
solution to this problem.
It would also be great if there was an automatic way to generate a
"Deprecated" section of the release notes so people don't have to
actually bump into the wall to realize something is deprecated.
Jason
--
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
