Very nice. Will this be put somewhere persistent where new Sage developers can be expected to find it? E.g. as a supplement to the Developer's Guide.
I have one comment: In the current version, sage.misc.misc.deprecation has some steep limitations. Trac #9919 (along with #9907) fixes it so it can be used on non-function callables (e.g. methods). Trac #9907 moves it to sage.misc.decorators.deprecation. Trac #9976 patches Sphinx so decorated callables in general will not have their signature reduced to a generic one in the documentation. These tracs depend on each other in that order and they all need review (hint hint). Especially the relocation of the decorator should perhaps be kept in mind for the blog entry. Cheers, Johan On Nov 1, 11:30 am, Jason Grout <jason-s...@creativetrax.com> wrote: > On 11/1/10 12:23 AM, William Stein wrote: > > >http://sagemath.blogspot.com/2010/10/how-to-referee-sage-trac-tickets... > > Nice. I'll have more comments later, but I did notice that this: > > from sage.misc.misc import deprecation > deprecation("function_name is deprecated, using new_function_name instead!") > > came out in formatting wrong (the second line looks like this in my > firefox (3.6.12, osx snow leopard): > > deprecation("function_name is deprecated, using new > > Also, you may want to put in the Sage version number to give people a > clue about when to remove the function (see the second argument to > deprecation). > > Thanks, > > 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
