Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #103898 > unrolled thread

Re: Continuing indentation

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Continuing indentation Peter Otten <__peter__@web.de> - 2016-03-02 22:27 +0100

#103898 — Re: Continuing indentation

Skip Montanaro wrote:

> Running flake8 over some code which has if statements with multiple
> conditions like this:
> 
>     if (some_condition and
>         some_other_condition and
>         some_final_condition):
>         play_bingo()
> 
> the tool complains that the indentation of the conditions is the same
> as the next block.  In this particular case, the overall conditions
> are too long to string together on a single line. I tried placing a
> second space after the if keyword:
> 
>     if  (some_condition and
>          some_other_condition and
>          some_final_condition):
>         play_bingo()
> 
> which solves the matching indentation problem, but creates a multiple
> spaces after keyword problem.  My guess is that adding a space after
> the open paren would provoke a message as well.
> 
> I use GNU Emacs as my text editor, and its python mode.  I'm pretty
> happy with everything (been using it in its current state for several
> years).  Aside from manually or configure-ologically suppressing E129,
> is there a better way to break lines I'm missing which will make
> flake8 happy?

Manually inspecting the output of

$ cd /usr/lib/python3.4
$ find . -name \*.py -print0 | xargs -0 egrep 'if \([^:]+$' --color -A3

[...]

gives the impression that those who do care are a minority and that the most 
common workaround is an extra indent of four spaces.

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web