On 2017-05-15 15:56, Erik Bray wrote:
The point is that no matter how well motivated a coding guideline is
it's just that--a guideline (maybe even a very important one!). But
one never bend over backwards to write non-idiomatic, convoluted, or
not well-motivated code just to satisfy a guideline.
Totally +1
Too bad that too many people take the coverage script too literal.
For functions which are meant to be called directly by end users,
doctests are essential because they should show examples of how the
function should actually be used. However, for internal functions or
things like __init__, it is often not easy to write meaningful
docstrings. Something I regularly see is that people literally write the
same doctest twice in two different places (say, an end-user function
and an internal function) just to satisfy a stupid script.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
