On 29Jun2019 10:19, Malcolm Greene <pyt...@bdurham.com> wrote:
I've also taken to having my files auto-formatted with yapf on save ...
@Cameron: Have you considered black at all and if so, what are your
thoughts?
I did consider black. Its core selling point was its total
inflexibility. Use this and stop _caring_ about the formatting: it will
be PEP8 compliant and readable. It is like "go fmt" in that regard
(Which I use with Go, when I use Go - you can see that in the "format"
script I posted).
The target here is: all code uses the same style, the chosen style is
good (readable, reasonable, acceptable to most people), let's just use
it and spent our time worrying about coding instead of style.
However, I want flexibility.
Like the OP, I use 2 spece indentation and have my own foibles. Here is
the .style.yapf file I use in my personal code:
[style]
based_on_style = pep8
blank_line_before_module_docstring = True
blank_line_before_nested_class_or_def = True
blank_lines_around_top_level_definition = 1
dedent_closing_brackets = True
#indent_dictionary_value = True
indent_width = 2
split_before_expression_after_opening_paren = True
split_before_first_argument = True
split_complex_comprehension = True
space_between_ending_comma_and_closing_bracket = False
split_before_dot = true
use_tabs = False
This comes remarkably close to the style I was hand applying before
biting the bullet and putting in the work required to get my editor to
autoformat on save.
[ Aside: another nice thing about autoformatting, over the "nice!"
feeling one gets seeing the code shuffle around in front of one's face,
is that if there's a syntax error the code _doesn't_ shuffle around and
one can go "whoops" and eyeball the code more closely. ]
Cheers,
Cameron Simpson <c...@cskk.id.au>
--
https://mail.python.org/mailman/listinfo/python-list
