blocks|key|622638|text|我就是这样做的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|622639|if+(collResv.repeatability+is+None+or
++++++++collResv.somethingElse):
++++collResv.rejected+=+True
++++collResv.rejectCompletely()|code-block|syntax|javascript|622640|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is what I do:

<pre><code>if (collResv.repeatability is None or
 collResv.somethingElse):
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

blocks|key|2763700|text|我经常通过在自己的语句中计算条件来解决这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2763701|condition+=+(collResv.repeatability+is+None+or
+++++++++++++collResv.somethingElse)
if+condition:
++++collResv.rejected+=+True
++++collResv.rejectCompletely()|code-block|syntax|javascript|2763702|不过，对于一个相对较短的条件(如您的具体示例)，我将使用nosklo的解决方案--这里使用的额外语句更适合于更长的条件表达式。|2763703|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Often I work around this problem by calculating the condition in an own statement:

<pre><code>condition = (collResv.repeatability is None or
 collResv.somethingElse)
if condition:
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

Though, for a still relatively short condition as in your specific example I'd go for nosklo's solution - the extra statement used here is more suited for even longer conditional expressions.

blocks|key|2763734|text|这是一个间接的答案--不是直接回答风格问题，而是一般的实际答案，所以值得一提的是。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2763735|我发现很少需要写多行条件词。这方面有两个因素：|2763736|2763737|不对80列的代码进行包装。PEP-8在这个问题上的建议是古老和有害的；我们已经过了80x25终端和编辑无法明智地处理包装的时代。100列是可以接受的，120列通常也是可以接受的。如果条件变得太长，仍然需要包装，那么将一些逻辑从条件中移出并放入单独的表达式通常是合理的。这也有助于提高可读性。|unordered-list-item|2763738|2763739|在我最近的项目中，大约12+12kloc，只有一个条件足够长，需要包装；这个问题很少出现。如果您确实需要这样做，那么就像nosklo所说的，分别缩进它--正如您注意到的，将它缩进与它下面的块相同的水平是令人困惑和难以理解的。|2763740|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|P|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

This is an indirect answer--not answering the style question directly, but it's the practical answer in general, so it's worth mentioning.

I find it extremely rare to need to write multi-line conditionals. There are two factors to this:

<ul>
<li>Don't wrap code at 80 columns. PEP-8's advice on this subject is ancient and harmful; we're well past the days of 80x25 terminals and editors that can't sensibly handle wrapping. 100 columns is fine, and 120 is usually acceptable, too.</li>
<li>If conditions become so long that they still need to wrap, it's usually reasonable to move some of the logic out of the conditional and into a separate expression. This also tends to help readability.</li>
</ul>

Grepping through my recent projects, around 12kloc, there's only one conditional long enough that it needed to be wrapped; the issue simply very rarely arises. If you do need to do this, then as nosklo says, indent it separately--as you noticed, indenting it to the same level as the block beneath it is confusing and hard to read.

blocks|key|644018|text|我有时会使用一个选项(尽管我并不完全相信它的可读性)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|644019|if+(collResv.repeatability+is+None+or
++++collResv.somethingElse
):
++++collResv.rejected+=+True
++++collResv.rejectCompletely()|code-block|syntax|javascript|644020|这样可能会更容易读懂：|644021|if+(
collResv.repeatability+is+None+or
collResv.somethingElse
):
++++collResv.rejected+=+True
++++collResv.rejectCompletely()|644022|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

An option I sometimes use (although I'm not completely sold on its readability):

<pre><code>if (collResv.repeatability is None or
 collResv.somethingElse
):
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

Possibly it would be more readable this way:

<pre><code>if (
collResv.repeatability is None or
collResv.somethingElse
):
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

blocks|key|644030|text|Pep-8推荐您缩进原始示例的方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|644031|现在，如果你愿意面对如此神圣的风格指南:-)你可以把操作员移到下一行：|644032|if+(collResv.repeatability+is+None
++++or+collResv.somethingElse):
++++collResv.rejected+=+True
++++collResv.rejectCompletely()|code-block|syntax|javascript|644033|我不太喜欢这一点，实际上我发现你原来的语法很容易读懂，而且不会花太多时间修改缩进或换行。|644034|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Pep-8 recommends the way you indented your original example.

Now if you're willing to fly in the face of the oh so sacred of style guides :-) you could move the operator to the next line:

<pre><code>if (collResv.repeatability is None
 or collResv.somethingElse):
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

I'm not really a fan of this, I actually find your original syntax fairly easy to read and wouldn't spend much time monkeying with the indentation or line breaks.

blocks|key|644048|text|在这种情况下，我只想：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|644049|if+(collResv.repeatability+is+None+or
++++collResv.somethingElse):
++++#+do:
++++collResv.rejected+=+True
++++collResv.rejectCompletely()|code-block|syntax|javascript|644050|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In such a case, I would simply do:

<pre><code>if (collResv.repeatability is None or
 collResv.somethingElse):
 # do:
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

blocks|key|2763888|text|我会这样做的。把它缩在很远的地方，以免弄糊涂。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2763889|if+(collResv.repeatability+is+None+or
++++++++++++++++++++++++++collResv.somethingElse):
++++collResv.rejected+=+True
++++collResv.rejectCompletely()|code-block|syntax|javascript|2763890|八号建议就在这里。|2763891|http://www.python.org/dev/peps/pep-0008/#indentation|offset|length|2763892|以下代码为建议|2763893|#+Aligned+with+opening+delimiter
foo+=+long_function_name(var_one,+var_two,
+++++++++++++++++++++++++var_three,+var_four)

#+More+indentation+included+to+distinguish+this+from+the+rest.
def+long_function_name(
++++++++var_one,+var_two,+var_three,
++++++++var_four):
++++print(var_one)|2763894|以下代码不建议|2763895|#+Arguments+on+first+line+forbidden+when+not+using+vertical+alignment
foo+=+long_function_name(var_one,+var_two,
++++var_three,+var_four)

#+Further+indentation+required+as+indentation+is+not+distinguishable
def+long_function_name(
++++var_one,+var_two,+var_three,
++++var_four):
++++print(var_one)|2763896|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|1G|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|14|8|@]|9|@$K|15|L|16|1|17]]|A|$]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1A|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|U|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|J]]]]

I would do it this way. Keep it indented far away not to get confused.

<pre><code>if (collResv.repeatability is None or
 collResv.somethingElse):
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

PEP-8 advise is right here.

<a href="http://www.python.org/dev/peps/pep-0008/#indentation" rel="nofollow">http://www.python.org/dev/peps/pep-0008/#indentation</a>

Below code is advised

<pre><code># Aligned with opening delimiter
foo = long_function_name(var_one, var_two,
 var_three, var_four)

# More indentation included to distinguish this from the rest.
def long_function_name(
 var_one, var_two, var_three,
 var_four):
 print(var_one)
</code></pre>

Below code is not advised

<pre><code># Arguments on first line forbidden when not using vertical alignment
foo = long_function_name(var_one, var_two,
 var_three, var_four)

# Further indentation required as indentation is not distinguishable
def long_function_name(
 var_one, var_two, var_three,
 var_four):
 print(var_one)
</code></pre>

blocks|key|622885|text|这里所有先前建议的一个问题是，后续条件的逻辑运算符放在前面的行中。海事组织，这使得它的可读性降低。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|622886|我建议将逻辑运算符与它附加到if语句的条件放在同一行。|622887|在我看来，这更好|622888|if+(None+==+foo
++++++++and+None+==+bar
++++++++or+None+==+foo_bar):|code-block|syntax|javascript|622889|比这更重要：|622890|if+(None+==+foo+and
++++++++None+==+bar+or
++++++++None+==+foo_bar):|622891|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

One problem with all previous suggestions here is that the logical operators for the subsequent conditions are put on the preceding line. Imo, that makes it less readable.

I recommend putting the logical operator on the same line as the condition it appends to the if statement.

This in my opinion, is better

<pre><code>if (None == foo
 and None == bar
 or None == foo_bar):
</code></pre>

than this:

<pre><code>if (None == foo and
 None == bar or
 None == foo_bar):
</code></pre>

blocks|key|644250|text|实际上，PEP-8在这里看起来很矛盾。虽然“最大行长”下面的示例显示了使用括号和标准的4字符缩进，但是对于函数声明，“缩进”部分表示，“进一步的缩进应该用来明确区分自己为连续行”。我不明白为什么这只限于"def“而不是"if”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|644251|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

PEP-8 actually seems contradictory here. While the example under "Maximum Line Length" shows the use of parentheses and a standard 4-character indent, the "Indentation" section says, with respect to function declarations, "further indentation should be used to clearly distinguish itself as a continuation line.". I don't see why this would be restricted only to "def" and not to "if".

When indenting long if conditions, you usually do something like this (actually, PyDev indents like that):

<pre><code>if (collResv.repeatability is None or
 collResv.somethingElse):
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

However, this puts the block started by the if statement on the same indentation level as the last part of the if condition which makes it very ugly/hard to read in my opinion as you don't immediately see where the block starts.

Some other styles I thought about:

<pre><code>if (collResv.repeatability is None or
 collResv.somethingElse):
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

This looks pretty inconsistent as the second line is indented much more than the first line but it's readable.

<pre><code>if (collResv.repeatability is None or
 collResv.somethingElse):
 collResv.rejected = True
 collResv.rejectCompletely()
</code></pre>

This is also more readable than the first example, but the indentation is not a multiple of 4 anymore and besides that it looks wrong as the second line has less indentation than the beginning of the condition in the first line.

<hr>

So, my main question is: Is there a suggested indentation style for cases like that which do not require overly-long lines (i.e. a single-line condition)?
If not, what do you prefer for cases like that?

Code-style for indention of multi-line 'if' statement?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在缩进长if条件时，通常会执行类似的操作(实际上，类似于PyDev缩进)：if (collResv.repeatability is None or    collResv.somethingElse):    collResv.rejected = True    collResv.rejectCompletely(...

问多行if语句缩进的代码样式？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问多行if语句缩进的代码样式？EN