On Mon, Mar 14, 2011 at 12:42 PM, Willem Jan Palenstijn <w...@usecode.org> wrote: > On Mon, Mar 14, 2011 at 05:44:26PM +0000, David Kirkby wrote: >> On 14 March 2011 16:42, Willem Jan Palenstijn <w...@usecode.org> wrote: >> > You can use hg to find out which commit added it, and if that commit is >> > recent enough it will have the trac ticket number in the commit message. >> > This is what version control systems are for... >> > >> >> It's often quite difficult to find the ticket though. I know the >> information is there, but its not so easy to find, whereas if the >> ticket number was a comment beside the doc test, it would be much >> easier. > > [Off-list reply since this is going off-topic]
? > You can use 'hg blame' or similar to get the revision in which a line/doctest > was changed, and then 'hg log -r revision' to get the commit message of that > revision. > > It's really a simple one-minute, two-step process. (And doesn't depend on > people keeping a growing list of ticket numbers for each doctest.) +1 That's what version control systems are for. (I think it's similarity silly to have to manually track changes in the SPKG.txt file). That being said, when there's a really odd test or corner case that just seems to come out of the blue, and a sensible explanation isn't easy to put in the docstring, I think saying "This tests that X from ticket #Y works::" is reasonable. - Robert -- 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
