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
Twisted's style guide is quite similar to PEP 8, except in a few places where it encodes a bit more information into the coding standard.
One place where it diverges is inter-function/inter-method vertical space separation. Python's guideline is 2-1-1: 2 lines between top-level suites, 1 line between functions, 1 line at your discretion to space out the implementation. Twisted's standard is 3-2-1: 3 between top-level suites, 2 between methods, 1 line between inner functions and at the user's discretion. This makes it a bit easier to visually scan for method endings, especially when methods often contain lots of callback functions.
Would it be possible to add a customization option to autopep8 to allow for these different blank-lines rules?
The text was updated successfully, but these errors were encountered:
Twisted's style guide is quite similar to PEP 8, except in a few places where it encodes a bit more information into the coding standard.
One place where it diverges is inter-function/inter-method vertical space separation. Python's guideline is 2-1-1: 2 lines between top-level suites, 1 line between functions, 1 line at your discretion to space out the implementation. Twisted's standard is 3-2-1: 3 between top-level suites, 2 between methods, 1 line between inner functions and at the user's discretion. This makes it a bit easier to visually scan for method endings, especially when methods often contain lots of callback functions.
Would it be possible to add a customization option to autopep8 to allow for these different blank-lines rules?
The text was updated successfully, but these errors were encountered: