The sage-coverage script doesn't handle cython files very well. I have an OLD ticket http://trac.sagemath.org/sage_trac/ticket/1795 addressing some of these issues. But I'm sure it doesn't currently apply. David
On Fri, May 25, 2012 at 2:39 PM, john_perry_usm <john.pe...@usm.edu> wrote: > Hello > > (1) I'm trying to bring doctest coverage of sage.numerical to 100%. > When I test for coverage, it says that, for example, the functions > add_variable() and solve() of glpk_backend.pyx are missing > documentation. > > But, they're *not* missing documentation. It's right there in the > file, immediately after the function declaration, just like all the > other functions that it *doesn't* complain about. It even appears in > the report: (notice the triple quote) > > Missing documentation: > * int add_variable(self, lower_bound=0.0, upper_bound=None, > binary=False, continuous=False, integer=False, obj=0.0, name=None) > except -1: """ Add a variable. This amounts to adding a new column to > the matrix. > > Does anyone know why I'm getting these reports? > > (2) I'm also getting requests to add a `TestSuite(s).run()` doctest. > Can someone tell me were I find instructions on how to add such a > doctest, or point me to a file that does contain such a doctest? > > thanks > john perry > > -- > 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 > -- 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
