From 26b0907345019dd59b04ea2e6fb4e57916f37f38 Mon Sep 17 00:00:00 2001 From: Daniel Bader Date: Wed, 24 May 2017 22:11:28 -0700 Subject: [PATCH] Migrate PEP 8 changes made in https://hg.python.org/peps/rev/c8554dfd4f22 --- index.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index aeb8320..c6dd348 100644 --- a/index.html +++ b/index.html @@ -303,8 +303,8 @@ if (this_is_one_thing and do_something() # Add some extra indentation on the conditional continuation line. -if (this_is_one_thing and - that_is_another_thing): +if (this_is_one_thing + and that_is_another_thing): do_something()

The closing brace/bracket/parenthesis on multi-line constructs may either line up under the first non-whitespace character of the last line of list, as in:

@@ -373,7 +373,7 @@ result = some_function_that_takes_arguments(

For decades the recommended style has been to break after binary operators. However, recent reseach unearthed recommendations by Donald Knuth to break before binary operators, in his writings about typesetting 4. Therefore it is permissible to break before or after a binary operator, as long as the convention is consistent locally. For new code Knuth's style is suggested.

-

Some examples of code beaking before binary Boolean operators:

+

Some examples of code breaking before binary Boolean operators:

class Rectangle(Blob):