I don't think we should mandate things so much, but it would be good to have a general policy about this. For example, we have a policy about error messages, but this is not absolute. In particular, this is about breaking ties when an author is doing something that a reviewer dislikes. I don't think effectively telling the community they can do whatever they like is so useful. (I suspect Frédéric could say a few words about this will all of the changes he has been doing to standardizing much of the code and documentation.) We should also be cognizant of the what is in the developer's manual can easily be interpreted as our convention choices/general policies (and has sometimes been referenced by reviewers in this manner).
Best, Travis On Wednesday, July 13, 2022 at 12:39:42 PM UTC+9 Kwankyu Lee wrote: > On Wednesday, July 13, 2022 at 12:13:28 PM UTC+9 John H Palmieri wrote: > >> I am "no" to having a Sage policy dictating blank lines, and I am also >> "no" to having a policy dictating no blank lines. >> > > We do have conventions in the developer manual by which sage developers > are "dictated". Specifically the blank line convention is suggested by > Examples in the developer manual: > > > https://doc.sagemath.org/html/en/developer/coding_basics.html#headings-of-sage-library-code-files > > So perhaps Travis wants to revise the Examples if we reach to a consensus. > > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/ddd430bf-ebdd-45a7-98c6-c2611405cf70n%40googlegroups.com.
