You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# CURRENT'"""\n A docstring\n """'# Expected'"""A docstring\n\n """'
Which for sure would be incompatible....
* Solution 1: Make `NumpydocSectionSpacingFormatter` not modify anything if there is only one section.
* Solution 2: Make `NumpydocSectionSpacingFormatter` by making it call the `ClosingQuotesFormatter` on its current output.
* Solution 2: Add a Formatter.conflcting atttribute (also entails fixing the tests so that one of the args is disabled)
* Op1: and check for conflicting formatters when calling _Run, warn about the behavior and disable all conflciting formatters.
* Op2: same but error out instead of warning (also entails changing the defaults)
Extras:
1. Improve documentation for closing-quotes to make the behavior more explicit.
--beginning-quotes, --no-beginning-quotes
Activate or deactivate beginning-quotes: Fix the position of the opening quotes. Styles: default. (default: True)
--closing-quotes, --no-closing-quotes
Activate or deactivate closing-quotes: Fix the position of the closing quotes. Styles: default. (default: True)
The text was updated successfully, but these errors were encountered:
Numpy refers to PEP256 in their introduction as well. If the docstring doesn't include any of the Numpy flavour we should default to the rules as defined by PEP256 which includes that one-line docstrings should be on one line.
It was discussed: #173
(check the whole conversation if you want more context)
Feature: two-pass formatting of the tokens #173 (comment)
The text was updated successfully, but these errors were encountered: