> solved). How do we handle these tickets ? Mark them as invalid/won't > fix/duplicates ? Give them a positive review ? > Maybe also add doctests (with a reference to the tickets) showing that the > problems are actually solved? > > Absolutely. We want to prevent regression. Another reason to do this is > that it's conceivable that the error was actually partly OS-dependent and > that was not recognized at the time, so that others testing the patch will > see that it still doesn't work. > > You're right though that some of them are unreasonable or hard to doctest. > How do we usually test timing ones? It's pretty machine-dependent, so it > might be hard to do properly.
There's also a (fixed) memory-leak : I am not sure if this can be doctested properly… Charles -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
