-
-
Notifications
You must be signed in to change notification settings - Fork 487
Commit
Remove excessive blank lines around INPUT, OUTPUT, EXAMPLES, and before docstring ending """. (#3)
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1415,7 +1415,6 @@ def __bool__(self) -> bool: | |
sage: b = Bar([4]) | ||
sage: not b | ||
False | ||
""" | ||
return bool(self._list) | ||
|
||
|
3 comments
on commit a2e9564
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
It seem that many authors like to put blank lines surrounding a list or a code example. When we later recommend developers to omit blank line following a block at the end of the text, someone may object. Let's see.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is important to have a binding decision upon such points. This improves consistency and makes the whole Sage project look more professional (and it inspires more serious work from developers and users). Consistency also has other practical benefits: it makes bulk changes easier as you don't need to search for weird formats and patterns.
Ideally, docstrings should pass through a script.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree.
No blank line above line 3103? I am not sure here. Please check again.