blocks|key|4588345|text|它的预期可能是这样的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4588346|RULES_LIST+=+[
++++('Name1',+1,+'Long+string+upto+40+chars'),
++++('Name2',+2,+'Long+string+upto+40+chars'),
++++('Name3',+3,+'Long+string+upto+40+chars'),
++++('Name4',+4,+'Long+string+upto+40+chars'),
++++('Name5',+5,+'Long+string+upto+40+chars'),
++++('Name6',+6,+'Long+string+upto+40+chars'),
++++('Name7',+7,+'Long+string+upto+40+chars'),
++++('Name8',+8,+'Long+string+upto+40+chars')
++++]|code-block|syntax|javascript|4588347|右方括号。|4588348|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|$]]

It was expecting maybe like this

<pre><code>RULES_LIST = [
 ('Name1', 1, 'Long string upto 40 chars'),
 ('Name2', 2, 'Long string upto 40 chars'),
 ('Name3', 3, 'Long string upto 40 chars'),
 ('Name4', 4, 'Long string upto 40 chars'),
 ('Name5', 5, 'Long string upto 40 chars'),
 ('Name6', 6, 'Long string upto 40 chars'),
 ('Name7', 7, 'Long string upto 40 chars'),
 ('Name8', 8, 'Long string upto 40 chars')
 ]
</code></pre>

the closing square bracket.

blocks|key|82024|text|您使用的是制表符而不是四个空格。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|82025|从pylint的角度来看，这三种可能性都是正确的，只要你使用四个空格而不是制表符，第一个就是black会使用的：|offset|length|82026|RULES_LIST+=+[
++++('Name1',+1,+'Long+string+upto+40+chars'),
++++('Name2',+2,+'Long+string+upto+40+chars'),
++++('Name3',+3,+'Long+string+upto+40+chars'),
++++('Name4',+4,+'Long+string+upto+40+chars'),
++++('Name5',+5,+'Long+string+upto+40+chars'),
++++('Name6',+6,+'Long+string+upto+40+chars'),
++++('Name7',+7,+'Long+string+upto+40+chars'),
++++('Name8',+8,+'Long+string+upto+40+chars'),
]

RULES_LIST+=+[('Name1',+1,+'Long+string+upto+40+chars'),
++++++++++++++('Name2',+2,+'Long+string+upto+40+chars'),
++++++++++++++('Name3',+3,+'Long+string+upto+40+chars'),
++++++++++++++('Name4',+4,+'Long+string+upto+40+chars'),
++++++++++++++('Name5',+5,+'Long+string+upto+40+chars'),
++++++++++++++('Name6',+6,+'Long+string+upto+40+chars'),
++++++++++++++('Name7',+7,+'Long+string+upto+40+chars'),
++++++++++++++('Name8',+8,+'Long+string+upto+40+chars')]

RULES_LIST+=+[
++++('Name1',+1,+'Long+string+upto+40+chars'),
++++('Name2',+2,+'Long+string+upto+40+chars'),
++++('Name3',+3,+'Long+string+upto+40+chars'),
++++('Name4',+4,+'Long+string+upto+40+chars'),
++++('Name5',+5,+'Long+string+upto+40+chars'),
++++('Name6',+6,+'Long+string+upto+40+chars'),
++++('Name7',+7,+'Long+string+upto+40+chars'),
++++('Name8',+8,+'Long+string+upto+40+chars')]|code-block|syntax|javascript|82027|请注意，在第一个示例中，有一个拖尾coma，这是为了减少您添加一行时的差异：|82028|添加第9行，但不包含尾随coma：|82029|+++++("Name7",+7,+"Long+string+upto+40+chars"),
-++++("Name8",+8,+"Long+string+upto+40+chars")
%2B++++("Name8",+8,+"Long+string+upto+40+chars"),
%2B++++("Name9",+9,+"Long+string+upto+40+chars")
+]|82030|添加带有尾随coma的第9行：|82031|+++++("Name8",+8,+"Long+string+upto+40+chars"),
%2B++++("Name9",+9,+"Long+string+upto+40+chars"),
+]|82032|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/psf/black^0|0|1A|5|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|F|3|G|5|H|7|17|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|H|7|1A|8|@]|9|@]|A|$I|J]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|H|7|1C|8|@]|9|@]|A|$I|J]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

You're using tabs instead of four spaces.

Those three possibilities are correct from pylint point of view, as long as you use four spaces instead of tabs, the first one is the one <a href="https://github.com/psf/black" rel="nofollow noreferrer">black</a> would use:

<pre><code>RULES_LIST = [
 ('Name1', 1, 'Long string upto 40 chars'),
 ('Name2', 2, 'Long string upto 40 chars'),
 ('Name3', 3, 'Long string upto 40 chars'),
 ('Name4', 4, 'Long string upto 40 chars'),
 ('Name5', 5, 'Long string upto 40 chars'),
 ('Name6', 6, 'Long string upto 40 chars'),
 ('Name7', 7, 'Long string upto 40 chars'),
 ('Name8', 8, 'Long string upto 40 chars'),
]

RULES_LIST = [('Name1', 1, 'Long string upto 40 chars'),
 ('Name2', 2, 'Long string upto 40 chars'),
 ('Name3', 3, 'Long string upto 40 chars'),
 ('Name4', 4, 'Long string upto 40 chars'),
 ('Name5', 5, 'Long string upto 40 chars'),
 ('Name6', 6, 'Long string upto 40 chars'),
 ('Name7', 7, 'Long string upto 40 chars'),
 ('Name8', 8, 'Long string upto 40 chars')]

RULES_LIST = [
 ('Name1', 1, 'Long string upto 40 chars'),
 ('Name2', 2, 'Long string upto 40 chars'),
 ('Name3', 3, 'Long string upto 40 chars'),
 ('Name4', 4, 'Long string upto 40 chars'),
 ('Name5', 5, 'Long string upto 40 chars'),
 ('Name6', 6, 'Long string upto 40 chars'),
 ('Name7', 7, 'Long string upto 40 chars'),
 ('Name8', 8, 'Long string upto 40 chars')]
</code></pre>

Note that, in the first one, there's a trailing coma, this is intended as it reduces differences when you add a line:

Adding a 9th line without trailing coma:

<pre><code> ("Name7", 7, "Long string upto 40 chars"),
- ("Name8", 8, "Long string upto 40 chars")
+ ("Name8", 8, "Long string upto 40 chars"),
+ ("Name9", 9, "Long string upto 40 chars")
 ]
</code></pre>

Adding a 9th line with trailing coma:

<pre><code> ("Name8", 8, "Long string upto 40 chars"),
+ ("Name9", 9, "Long string upto 40 chars"),
 ]
</code></pre>

blocks|key|82055|text|如果要继续使用选项卡，可以在.pylintrc文件中更改以下设置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|82056|indent-string='\t'
indent-after-paren=1|code-block|syntax|javascript|82057|如果只更改第一个，pylint将使用四个制表符来进行缩进。|82058|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|$]]

If you want to continue using tabs, you can change the following settings in the .pylintrc file:

<pre><code>indent-string='\t'
indent-after-paren=1
</code></pre>

If you only change the first one, pylint will expect four tabs to be used for indentation.

blocks|key|82112|text|我不想费心修改配置文件，所以我发现最简单的解决方案是在检查之前简单地将制表符转换为空格：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|82113|expand+--tabs=4+$filename+%7C+pylint+--from-stdin+stdin|code-block|syntax|javascript|82114|注意:这需要pylint+2.4才能工作。一定要仔细检查这个版本，因为当我把上面这行代码打包到一个自定义的pylint检查脚本中时，它决定使用一个不同版本的pylint，而不是终端给我的那个。|82115|下面是mylint脚本的一个大大缩写的版本，您可以根据自己的需要进行编辑：|82116|set+-e
pylint="/usr/bin/pylint"

#Warnings+that+I+don't+care+about:
disabler(){
echo+no-else-return+++++++++++++#No+else+after+return
echo+pointless-string-statement
echo+no-self-use++++++++++++++++#Class+method+without+a+self.+in+it.
echo+useless-else-on-loop+++++++#For+else+loop+where+the+else+isn't+needed
echo+too-many-locals++++++++++++#More+than+15+local+vars
echo+cell-var-from-loop+++++++++#https://stackoverflow.com/questions/25314547/cell-var-from-loop-warning-from-pylint
echo+no-else-continue+++++++++++#No+else+after+contiune+statement
echo+no-else-break++++++++++++++#No+else+after+break+statement
echo+C0114,C0116++++++++++++++++#Docstring+nonsense

echo+W0614,W0401++++++++++++++++#Wildcard+imports+are+fixed+by+star_namer.py
}

expand+--tabs=4+$1+%7C+$pylint+--from-stdin+stdin+--max-line-length=120+--variable-rgx="[a-z0-9_]{1,30}$"+--disable=`disabler+%7C+tr+'\n'+','`+--docstring-min-length=5+--min-public-methods=1++%7C+sed+G+%7C+less|82117|这是很好的能够评论，很容易取消评论的警告，并留下一个小笔记，这样我就不会忘记他们做了什么。|82118|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|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I didn't want to bother messing with a config file, so I found the easiest solution was to simply convert the tabs into spaces before checking:
<pre><code>expand --tabs=4 $filename | pylint --from-stdin stdin
</code></pre>
Note: This requires pylint 2.4 to work. Make sure you double check the version, because when I wrapped the above line into a custom pylint checker script it decided to use a different version of pylint mysteriously installed elsewhere on the system, instead of the one the terminal gave me.
Here's a heavily abbreviated version of the mylint script that you can edit as you see fit:
<pre><code>set -e
pylint=&quot;/usr/bin/pylint&quot;

#Warnings that I don't care about:
disabler(){
echo no-else-return #No else after return
echo pointless-string-statement
echo no-self-use #Class method without a self. in it.
echo useless-else-on-loop #For else loop where the else isn't needed
echo too-many-locals #More than 15 local vars
echo cell-var-from-loop #https://stackoverflow.com/questions/25314547/cell-var-from-loop-warning-from-pylint
echo no-else-continue #No else after contiune statement
echo no-else-break #No else after break statement
echo C0114,C0116 #Docstring nonsense

echo W0614,W0401 #Wildcard imports are fixed by star_namer.py
}

expand --tabs=4 $1 | $pylint --from-stdin stdin --max-line-length=120 --variable-rgx=&quot;[a-z0-9_]{1,30}$&quot; --disable=`disabler | tr '\n' ','` --docstring-min-length=5 --min-public-methods=1 | sed G | less
</code></pre>
It's nice to be able to comment, uncomment the warnings easily and leave a little note so I don't forget what they do.

I am trying to properly indent following piece of code:

<pre><code>RULES_LIST = [
 ('Name1', 1, 'Long string upto 40 chars'),
 ('Name2', 2, 'Long string upto 40 chars'),
 ('Name3', 3, 'Long string upto 40 chars'),
 ('Name4', 4, 'Long string upto 40 chars'),
 ('Name5', 5, 'Long string upto 40 chars'),
 ('Name6', 6, 'Long string upto 40 chars'),
 ('Name7', 7, 'Long string upto 40 chars'),
 ('Name8', 8, 'Long string upto 40 chars')
]
</code></pre>

Pylint complains <code>Wrong hanging indentation.</code> for above code, and PEP8 complains <code>E121: under-indented for hanging indent</code>.

A possible fix for pylint is changing it to:

<pre><code>RULES_LIST = [\
 ('Name1', 1, 'Long string upto 40 chars'),
 ...
 ('Name8', 8, 'Long string upto 40 chars')]
</code></pre>

but PEP8 complains <code>E121 and E502</code>

PEP8: 1.5.7 (default configuration) 
Pylint: 1.3.0 (default configuration) 
Python: 2.7.5 (Running on OSX 10.9.3)

The list can grow longer. Can someone please suggest a proper indentation for this?

How to fix Pylint "Wrong hanging indentation" and PEP8 E121?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在尝试适当地缩进以下代码：RULES_LIST = [    ('Name1', 1, 'Long string upto 40 chars'),    ('Name2', 2, 'Long string upto 40 chars'),    ('Name3', 3, 'Long string upto 40 c...

问如何修复Pylint“错误的悬空缩进”和PEP8 E121？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复Pylint“错误的悬空缩进”和PEP8 E121？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复Pylint“错误的悬空缩进”和PEP8 E121？
EN