Question

我在C＃应用程序中托管IronPython，并将主机的API注入全局范围。

我刚开始喜欢syntastic，因为vim使用pylint来检查我的脚本。但是我对所注入变量的所有[E0602, method_name] Undefined variable 'variable_name'错误消息感到恼火。

我知道使用# pylint: disable=E0602来禁用此错误消息，但我不想仅为某些特定变量名称削弱一个非常有用的功能。

你是如何处理的？

目前，我在我的脚本顶部执行此操作：

try:
    host_object = getattr(__builtins__, 'host_object')
except AttributeError:
    pass # oops, run this script inside the host application!!

我真正想做的是：

# pylint: declare=host_object, other_stuff

Answer 1

您可以将变量添加到'additional-builtins'选项中，以便pylint将其视为已定义。

这必须在rc文件中完成，不能在代码中内联。

Answer 2

在代码中禁用E0602：

# make pylint think that it knows about 'injected_var' variable
injected_var = injected_var  # pylint:disable=invalid-name,used-before-assignment

显然，每个模块需要执行一次，在此行之后出现的所有injected_var对于pylint都是合法的。

Answer 3

对此有good-names=host_object,other_stuff或additional-builtins=...，或者对于某些高级内容，您可以通过variable-rgx修改正则表达式。

Answer 4

不适用于变量，但您可以为具有var的行禁用它。请参阅ref。

Answer 5

我刚遇到这个问题，我刚刚在pylintrc文件中添加了禁用选项。在我的情况下，我正在编写一个小脚本，一些pylint检查有点矫枉过正。所以我禁用了未定义的变量错误

E: 32,40: Undefined variable 'description' (undefined-variable)

通过

禁用= E0602，E0603

您可以在http://pylint-messages.wikidot.com/all-codes

找到代码和含义

我的pylintrc文件：

# The format of this file isn't really documented; just use --generate-rcfile
[MASTER]
# Add <file or directory> to the black list. It should be a base name, not a
# path. You may set this option multiple times.
#
# dirname, then we'll need to expand the ignore features in pylint :/
ignore=.git,tools, etc
[MESSAGES CONTROL]
# NOTE(gus): This is a long list.  A number of these are important and
# should be re-enabled once the offending code is fixed (or marked
# with a local disable)
disable=E0602, E0603,
# "F" Fatal errors that prevent further processing
 import-error,
# "I" Informational noise
 locally-disabled,
# "E" Error for important programming issues (likely bugs)
 access-member-before-definition,
 no-member,
 no-method-argument,
 no-self-argument,
# "W" Warnings for stylistic problems or minor programming issues
 abstract-method,
 arguments-differ,
 attribute-defined-outside-init,
 bad-builtin,
 bad-indentation,
 broad-except,
 dangerous-default-value,
 deprecated-lambda,
 deprecated-module,
 duplicate-key,
 expression-not-assigned,
 fixme,
 global-statement,
 no-init,
 non-parent-init-called,
 not-callable,
 protected-access,
 redefined-builtin,
 redefined-outer-name,
 signature-differs,
 star-args,
 super-init-not-called,
 super-on-old-class,
 unpacking-non-sequence,
 unused-argument,
 unused-import,
# "C" Coding convention violations
 invalid-name,
 missing-docstring,
 superfluous-parens,
 bad-continuation,
 Undefined variable,
# "R" Refactor recommendations
 abstract-class-little-used,
 abstract-class-not-used,
 duplicate-code,
 interface-not-implemented,
 no-self-use,
 too-few-public-methods,
 too-many-ancestors,
 too-many-arguments,
 too-many-branches,
 too-many-instance-attributes,
 too-many-lines,
 too-many-locals,
 too-many-public-methods,
 too-many-return-statements,
 too-many-statements


[BASIC]
# Variable names can be 1 to 31 characters long, with lowercase and underscores
variable-rgx=[a-z_][a-z0-9_]{0,30}$

# Argument names can be 2 to 31 characters long, with lowercase and underscores
argument-rgx=[a-z_][a-z0-9_]{1,30}$

# Method names should be at least 3 characters long
# and be lowecased with underscores
method-rgx=([a-z_][a-z0-9_]{2,}|setUp|tearDown)$

# Module names matching vulcan-* are ok (files in bin/)
# module-rgx=(([a-z_][a-z0-9_]*)|([A-Z][a-zA-Z0-9]+)|(vulcan-[a-z0-9_-]+))$
module-rgx=(([a-z_][a-z0-9_]*)|([A-Z][a-zA-Z0-9]+)|([a-z0-9_-]+))$



# Don't require docstrings on tests.
no-docstring-rgx=((__.*__)|([tT]est.*)|setUp|tearDown)$

[FORMAT]
# Maximum number of characters on a single line.
max-line-length=79

[VARIABLES]
# List of additional names supposed to be defined in builtins. Remember that
# you should avoid to define new builtins when possible.
# _ is used by our localization
additional-builtins=_

[CLASSES]
# List of interface methods to ignore, separated by a comma.
ignore-iface-methods=

[IMPORTS]
# Deprecated modules which should not be used, separated by a comma
deprecated-modules=
# should use openstack.common.jsonutils
 json

[TYPECHECK]
# List of module names for which member attributes should not be checked
ignored-modules=six.moves,_MovedItems

[REPORTS]
# Tells whether to display a full report or only the messages
reports=no

Answer 6

实际上，通过在dummy-variables-rgx（或旧{{1}中的dummy-variables中指定，可以通过方式来禁用有关特定未定义变量的的pylint争论版本）。 pylint默认包含dummy-variables，并在_,dummy执行时使用用户指定的值覆盖：

pylint

或旧$ pylint --dummy-variables-rgx='(_+[a-zA-Z0-9]*?$)|dummy|host_object'版本：

pylint

如果VSCode的$ pylint --dummy-variables='_,dummy,host_object'配置可以通过按 Ctrl + ，打开pylint：

User/Workspace Settings

Answer 7

把这个贴在行尾，你就完成了：

# noqa

如何为文件中的特定变量禁用pylint“未定义变量”错误？

7 个答案: