-
Notifications
You must be signed in to change notification settings - Fork 58
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
Formatting settings? #209
Comments
I don't usually use autoformatters, most of them are downright terrible. clang-format is okay but this isn't a C project. |
@whitequark Thoughts on adding a flake8 step to Travis that checks immediately whether the code is properly formatted (based on the rules you decide- i.e. remove the restrictive 80 char per line limit), and fails if it's not? |
I'm not sure if there's much point to it. |
I prefer to leave formatting up to the auto-formatter so that I don't have to do any formatting myself. Specifying the project policy as no auto-formatting, though, is perfectly fine. I'll just have to remember to turn the auto-formatter off when I write code for nMigen :) |
Yeah, I would prefer no autoformatting for now. Could perhaps be changed in the future. |
Somewhat annoyingly, |
That's what |
What's the point of using yapf if you disable it on 99% of code? |
The board files aren't 99% of the code, are they? |
They are 99% of code in nmigen-boards (which is a different repository with different tooling settings). |
Does the project use yapf, autopep8, or black for standard auto-formatting? Any special parameters passed to these?
The text was updated successfully, but these errors were encountered: