Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: twisted-style formatting #359

Open
glyph opened this issue Nov 11, 2017 · 0 comments
Open

feature request: twisted-style formatting #359

glyph opened this issue Nov 11, 2017 · 0 comments

Comments

@glyph
Copy link

glyph commented Nov 11, 2017

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant