blocks|key|167268|text|可能，它与NumPy的方法导入的深奥方法混淆了。也就是说，zeros实际上是numpy.core.multiarray.zeros，通过以下语句导入到NumPy中|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|167269|from+.core+import+*|code-block|syntax|javascript|167270|依次使用导入|167271|from+.numeric+import+*|167272|在数字中你会发现|167273|zeros+=+multiarray.zeros|167274|我想我会在Pylint的位置上感到困惑！|167275|有关视图的Pylint侧，请参见this+bug。|167276|entityMap|0|LINK|mutability|MUTABLE|url|https://bitbucket.org/logilab/pylint/issue/58/false-positive-no-member-on-numpy-imports^0|T|5|12|R|0|0|0|0|0|0|0|G|8|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1A|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1C|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1E|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1F|8|@]|D|@$9|1G|A|1H|1|1I]]|E|$]]|$1|W|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]]]

Probably, it's confused with NumPy's abstruse method of methods import. Namely, <code>zeros</code> is in fact <code>numpy.core.multiarray.zeros</code>, imported in NumPy with the statement
<pre><code>from .core import *
</code></pre>
in turn imported with
<pre><code>from .numeric import *
</code></pre>
and in numeric you'll find
<pre><code>zeros = multiarray.zeros
</code></pre>
I guess I would be confused in place of Pylint!
See <a href="https://bitbucket.org/logilab/pylint/issue/58/false-positive-no-member-on-numpy-imports" rel="nofollow noreferrer">this bug</a> for the Pylint side of view.

blocks|key|2765708|text|在过去的几年里，有很多关于这个问题的不同的bug的报道，比如https://bitbucket.org/logilab/pylint/issue/58/false-positive-no-member-on-numpy-imports|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2765709|我建议禁用发生投诉的线路。|2765710|#+pylint:+disable=E1103
print+np.zeros([1,+4])
#+pylint:+enable=E1103|code-block|syntax|javascript|2765711|entityMap|0|LINK|mutability|MUTABLE|url|https://bitbucket.org/logilab/pylint/issue/58/false-positive-no-member-on-numpy-imports^0|U|2F|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

There have been many different bugs reported about this over the past few years i.e. <a href="https://bitbucket.org/logilab/pylint/issue/58/false-positive-no-member-on-numpy-imports" rel="noreferrer">https://bitbucket.org/logilab/pylint/issue/58/false-positive-no-member-on-numpy-imports</a>

I'd suggest disabling for the lines where the complaints occur.

<pre><code># pylint: disable=E1103
print np.zeros([1, 4])
# pylint: enable=E1103
</code></pre>

blocks|key|2978613|text|我在使用NumPy、SciPy、sklearn、nipy等时遇到了这个问题，我通过像这样包装epylint解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2978614|文件epylint.py|2978615|#!/usr/bin/python

"""
Synopsis:+epylint+wrapper+that+filters+a+bunch+of+false-positive+warnings+and+errors
Author:+DOHMATOB+Elvis+Dopgima+<gmdopp@gmail.com>+<elvis.dohmatob@inria.fr>

"""

import+os
import+sys
import+re
from+subprocess+import+Popen,+STDOUT,+PIPE

NUMPY_HAS_NO_MEMBER+=+re.compile("Module+'numpy(?:\..%2B)?'+has+no+'.%2B'+member")
SCIPY_HAS_NO_MEMBER+=+re.compile("Module+'scipy(?:\..%2B)?'+has+no+'.%2B'+member")
SCIPY_HAS_NO_MEMBER2+=+re.compile("No+name+'.%2B'+in+module+'scipy(?:\..%2B)?'")
NIPY_HAS_NO_MEMBER+=+re.compile("Module+'nipy(?:\..%2B)?'+has+no+'.%2B'+member")
SK_ATTR_DEFINED_OUTSIDE_INIT+=+re.compile("Attribute+'.%2B_'+defined+outside+__init__")
REL_IMPORT_SHOULD_BE+=+re.compile("Relative+import+'.%2B',+should+be+'.%2B")
REDEFINING_NAME_FROM_OUTER_SCOPE+=+re.compile("Redefining+name+'.%2B'+from+outer+scope")

if+__name__+==+"__main__":
++++basename+=+os.path.basename(sys.argv[1])
++++for+line+in+Popen(['epylint',+sys.argv[1],+'--disable=C,R,I'++#+filter+thesew+arnings
+++++++++++++++++++++++],+stdout=PIPE,+stderr=STDOUT,+universal_newlines=True).stdout:
++++++++if+line.startswith("***********"):
++++++++++++continue
++++++++elif+line.startswith("No+config+file+found,"):
++++++++++++continue
++++++++elif+"anomalous-backslash-in-string,"+in+line:
++++++++++++continue
++++++++if+NUMPY_HAS_NO_MEMBER.search(line):
++++++++++++continue
++++++++if+SCIPY_HAS_NO_MEMBER.search(line):
++++++++++++continue
++++++++if+SCIPY_HAS_NO_MEMBER2.search(line):
++++++++++++continue
++++++++if+"Used+*+or+**+magic"+in+line:
++++++++++++continue
++++++++if+"No+module+named"+in+line+and+"_flymake"+in+line:
++++++++++++continue
++++++++if+SK_ATTR_DEFINED_OUTSIDE_INIT.search(line):
++++++++++++continue
++++++++if+"Access+to+a+protected+member"+in+line:
++++++++++++continue
++++++++if+REL_IMPORT_SHOULD_BE.search(line):
++++++++++++continue
++++++++if+REDEFINING_NAME_FROM_OUTER_SCOPE.search(line):
++++++++++++continue
++++++++if+NIPY_HAS_NO_MEMBER.search(line):
++++++++++++continue
++++++++#+XXX+extend+by+adding+more+handles+for+false-positives+here
++++++++else:
++++++++++++print+line,|code-block|syntax|javascript|2978616|此脚本只需运行epylint，然后抓取其输出以过滤掉误报警告和错误。你可以通过添加更多的elif案例来扩展它。|2978617|注意:如果这适用于您，那么您需要修改您的pychechers.sh，使其如下所示|2978618|#!/bin/bash

epylint.py+"$1"+2>/dev/null
pyflakes+"$1"
pep8+--ignore=E221,E701,E202+--repeat+"$1"
true|2978619|(当然，您必须首先使epylint.py成为可执行文件。)|2978620|这是我的.emacs+https://github.com/dohmatob/mydotemacs的链接。|offset|length|2978621|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dohmatob/mydotemacs^0|0|0|0|0|0|0|0|B|12|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|17|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@$S|1A|T|1B|1|1C]]|A|$]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

I had this problem with NumPy, SciPy, sklearn, nipy, etc., and I solved it by wrapping epylint like so:
<h3>File epylint.py</h3>
<pre><code>#!/usr/bin/python

&quot;&quot;&quot;
Synopsis: epylint wrapper that filters a bunch of false-positive warnings and errors
Author: DOHMATOB Elvis Dopgima &lt;gmdopp@gmail.com&gt; &lt;elvis.dohmatob@inria.fr&gt;

&quot;&quot;&quot;

import os
import sys
import re
from subprocess import Popen, STDOUT, PIPE

NUMPY_HAS_NO_MEMBER = re.compile(&quot;Module 'numpy(?:\..+)?' has no '.+' member&quot;)
SCIPY_HAS_NO_MEMBER = re.compile(&quot;Module 'scipy(?:\..+)?' has no '.+' member&quot;)
SCIPY_HAS_NO_MEMBER2 = re.compile(&quot;No name '.+' in module 'scipy(?:\..+)?'&quot;)
NIPY_HAS_NO_MEMBER = re.compile(&quot;Module 'nipy(?:\..+)?' has no '.+' member&quot;)
SK_ATTR_DEFINED_OUTSIDE_INIT = re.compile(&quot;Attribute '.+_' defined outside __init__&quot;)
REL_IMPORT_SHOULD_BE = re.compile(&quot;Relative import '.+', should be '.+&quot;)
REDEFINING_NAME_FROM_OUTER_SCOPE = re.compile(&quot;Redefining name '.+' from outer scope&quot;)

if __name__ == &quot;__main__&quot;:
 basename = os.path.basename(sys.argv[1])
 for line in Popen(['epylint', sys.argv[1], '--disable=C,R,I' # filter thesew arnings
 ], stdout=PIPE, stderr=STDOUT, universal_newlines=True).stdout:
 if line.startswith(&quot;***********&quot;):
 continue
 elif line.startswith(&quot;No config file found,&quot;):
 continue
 elif &quot;anomalous-backslash-in-string,&quot; in line:
 continue
 if NUMPY_HAS_NO_MEMBER.search(line):
 continue
 if SCIPY_HAS_NO_MEMBER.search(line):
 continue
 if SCIPY_HAS_NO_MEMBER2.search(line):
 continue
 if &quot;Used * or ** magic&quot; in line:
 continue
 if &quot;No module named&quot; in line and &quot;_flymake&quot; in line:
 continue
 if SK_ATTR_DEFINED_OUTSIDE_INIT.search(line):
 continue
 if &quot;Access to a protected member&quot; in line:
 continue
 if REL_IMPORT_SHOULD_BE.search(line):
 continue
 if REDEFINING_NAME_FROM_OUTER_SCOPE.search(line):
 continue
 if NIPY_HAS_NO_MEMBER.search(line):
 continue
 # XXX extend by adding more handles for false-positives here
 else:
 print line,
</code></pre>
This script simply runs epylint, and then scrapes its output to filter out false-positive warnings and errors. You can extend it by added more elif cases.
N.B.: If this applies to you, then you'll want to modify your pychechers.sh so it likes like this
<pre><code>#!/bin/bash

epylint.py &quot;$1&quot; 2&gt;/dev/null
pyflakes &quot;$1&quot;
pep8 --ignore=E221,E701,E202 --repeat &quot;$1&quot;
true
</code></pre>
(Of course, you have to make epylint.py executable first.)
Here is a link to my .emacs <a href="https://github.com/dohmatob/mydotemacs" rel="nofollow noreferrer">https://github.com/dohmatob/mydotemacs</a>.

blocks|key|168240|text|我必须在我经常使用NumPy的任何文件的顶部添加此代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|168241|#+To+ignore+numpy+errors:
#+++++pylint:+disable=E1101|code-block|syntax|javascript|168242|以防eclipse里的人在使用Pydev和pylint时遇到麻烦...|168243|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|$]]

I had to add this at the top of any file where I use NumPy a lot.
<pre><code># To ignore numpy errors:
# pylint: disable=E1101
</code></pre>
Just in case someone in eclipse is having trouble with Pydev and pylint...

blocks|key|2765808|text|这是我为这个问题想出的伪解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2765809|#pylint:+disable=no-name-in-module
from+numpy+import+array+as+np_array,+transpose+as+np_transpose,+\
++++++linspace+as+np_linspace,+zeros+as+np_zeros
from+numpy.random+import+uniform+as+random_uniform
#pylint:+enable=no-name-in-module|code-block|syntax|javascript|2765810|然后，在你的代码中，不是像np.array和np.zeros那样调用NumPy函数，而是编写np_array、np_zeros等。这种方法与其他答案中提出的其他方法相比具有以下优点：|offset|length|style|CODE|2765811|Pylint+disable/enable仅限于代码的一小部分，这意味着您不必用Pylint+directive.|2765812|You将调用NumPy函数的每一行都括起来，而不是对整个文件执行Pylint+disable+|unordered-list-item|2765813|
|2765814|，这可能会掩盖代码中的其他问题。|2765815|2765816|明显的缺点是，您必须显式地导入您使用的每个NumPy函数。该方法可以进一步详细说明。您可以定义自己的模块，将其命名为numpy_importer，如下所示|2765817|"""+module:+numpy_importer.py
+++++++explicitely+import+numpy+functions+while+avoiding+Pylint+errors
"""
#pylint:+disable=unused-import
#pylint:+disable=no-name-in-module
from+numpy+import+array,+transpose,+zeros++#add+all+things+you+need
from+numpy.random+import+uniform+as+random_uniform
#pylint:+enable=no-name-in-module|2765818|然后，您的应用程序代码只能将此模块(而不是NumPy)导入为|2765819|import+numpy_importer+as+np|2765820|并照常使用名称：np.zeros、np.array等。|2765821|这样做的好处是，您将拥有一个模块，在该模块中，所有与NumPy相关的导入都是一次性完成的，然后您可以使用这一行将其导入到您想要的任何位置。不过，您必须注意，numpy_importer不会导入NumPy中不存在的名称，因为这些错误不会被Pylint捕获。|2765822|entityMap^0|0|0|D|8|M|8|1A|8|1J|8|0|0|0|0|0|0|1M|E|0|0|0|0|8|8|H|8|0|26|E|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@$I|1D|J|1E|K|L]|$I|1F|J|1G|K|L]|$I|1H|J|1I|K|L]|$I|1J|J|1K|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1L|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1M|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1N|8|@]|9|@]|A|$]]|$1|T|3|U|5|Q|7|1O|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1Q|8|@$I|1R|J|1S|K|L]]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|1T|8|@]|9|@]|A|$E|F]]|$1|10|3|11|5|6|7|1U|8|@]|9|@]|A|$]]|$1|12|3|13|5|D|7|1V|8|@]|9|@]|A|$E|F]]|$1|14|3|15|5|6|7|1W|8|@$I|1X|J|1Y|K|L]|$I|1Z|J|20|K|L]]|9|@]|A|$]]|$1|16|3|17|5|6|7|21|8|@$I|22|J|23|K|L]]|9|@]|A|$]]|$1|18|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|19|$]]

This is the pseudo-solution I have come up with for this problem.
<pre><code>#pylint: disable=no-name-in-module
from numpy import array as np_array, transpose as np_transpose, \
 linspace as np_linspace, zeros as np_zeros
from numpy.random import uniform as random_uniform
#pylint: enable=no-name-in-module
</code></pre>
Then, in your code, instead of calling NumPy functions as <code>np.array</code> and <code>np.zeros</code> and so on, you would write <code>np_array</code>, <code>np_zeros</code>, etc.
Advantages of this approach vs. other approaches suggested in other answers:
<ul>
<li>The Pylint disable/enable is restricted to a small region of your code</li>
<li>That means that you don't have to surround every single line that has an invocation of a NumPy function with a Pylint directive.</li>
<li>You are not doing Pylint disable of the error for your whole file, which might mask other issues with your code.</li>
</ul>
The clear disadvantage is that you have to explicitly import every NumPy function you use.
The approach could be elaborated on further.
You could define your own module, call it say, <code>numpy_importer</code> as follows
<pre><code>&quot;&quot;&quot; module: numpy_importer.py
 explicitely import numpy functions while avoiding Pylint errors
&quot;&quot;&quot;
#pylint: disable=unused-import
#pylint: disable=no-name-in-module
from numpy import array, transpose, zeros #add all things you need
from numpy.random import uniform as random_uniform
#pylint: enable=no-name-in-module
</code></pre>
Then, your application code could import this module only (instead of NumPy) as
<pre><code>import numpy_importer as np
</code></pre>
and use the names as usual: <code>np.zeros</code>, <code>np.array</code> etc.
The advantage of this is that you will have a single module in which all NumPy related imports are done once and for all, and then you import it with that single line, wherever you want. Still you have to be careful that <code>numpy_importer</code> does not import names that don’t exist in NumPy as those errors won't be caught by Pylint.

blocks|key|2978717|text|因为这是谷歌搜索的最高结果，它给我的印象是你必须忽略所有文件中的警告：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2978718|这个问题实际上已经在上个月https://bitbucket.org/logilab/astroid/commits/83d78af4866be5818f193360c78185e1008fd29e的Pylint/astroid的源代码中得到了修复，但还没有出现在Ubuntu包中。|offset|length|2978719|要获取源代码，只需|2978720|hg+clone+https://bitbucket.org/logilab/pylint/
hg+clone+https://bitbucket.org/logilab/astroid
mkdir+logilab+&&+touch+logilab/__init__.py
hg+clone+http://hg.logilab.org/logilab/common+logilab/common
cd+pylint+&&+python+setup.py+install|code-block|syntax|javascript|2978721|因此最后一步很可能需要一个sudo，当然你也需要Mercurial来克隆。|style|CODE|2978722|entityMap|0|LINK|mutability|MUTABLE|url|https://bitbucket.org/logilab/astroid/commits/83d78af4866be5818f193360c78185e1008fd29e^0|0|D|2E|0|0|0|0|D|4|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@$D|16|E|17|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Since this is the top result in Google Search and it gave me the impression that you have to ignore those warnings in all files:
The problem has actually been fixed in the sources of Pylint/astroid last month <a href="https://bitbucket.org/logilab/astroid/commits/83d78af4866be5818f193360c78185e1008fd29e" rel="nofollow noreferrer">https://bitbucket.org/logilab/astroid/commits/83d78af4866be5818f193360c78185e1008fd29e</a>
but are not yet in the Ubuntu packages.
To get the sources, just
<pre><code>hg clone https://bitbucket.org/logilab/pylint/
hg clone https://bitbucket.org/logilab/astroid
mkdir logilab &amp;&amp; touch logilab/__init__.py
hg clone http://hg.logilab.org/logilab/common logilab/common
cd pylint &amp;&amp; python setup.py install
</code></pre>
whereby the last step will most likely require a <code>sudo</code> and of course you need Mercurial to clone.

blocks|key|2978740|text|我一直在开发Pylint的补丁，以解决NumPy等库中动态成员的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2978741|它添加了一个"dynamic-modules“选项，强制在运行时通过真正导入模块来检查成员是否存在。参见Issue+#413+in+logilab/pylint。还有一个拉取请求；请参阅其中一条评论中的链接。|offset|length|2978742|entityMap|0|LINK|mutability|MUTABLE|url|https://bitbucket.org/logilab/pylint/issue/413/add-dynamic-modules-option-to-allow-for^0|0|1G|S|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I've been working on a patch to Pylint to solve the issue with dynamic members in libraries such as NumPy.
It adds a &quot;dynamic-modules&quot; option which forces to check if members exist during runtime by making a real import of the module. See <a href="https://bitbucket.org/logilab/pylint/issue/413/add-dynamic-modules-option-to-allow-for" rel="nofollow noreferrer">Issue #413 in logilab/pylint</a>. There is also a pull request; see link in one of the comments.

blocks|key|167352|text|我在这里遇到了同样的问题，即使是所有相关包的最新版本(astroid+1.3.2、logilab_common+0.63.2、pylon+1.4.0)也是如此。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|167353|下面的解决方案非常好用:我在[TYPECHECK]部分修改了我的pylintrc文件，将numpy添加到了被忽略的模块列表中：|167354|[TYPECHECK]

ignored-modules+=+numpy|code-block|syntax|javascript|167355|根据错误，您可能还需要添加以下行(仍在[TYPECHECK]+section中)：|167356|ignored-classes+=+numpy|167357|entityMap^0|R|D|15|L|1R|B|0|E|B|W|8|18|5|0|0|J|J|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|R|$]]

I had the same issue here, even with the latest versions of all related packages (<code>astroid 1.3.2</code>, <code>logilab_common 0.63.2</code>, <code>pylon 1.4.0</code>).

The following solution worked like a charm: I added <code>numpy</code> to the list of ignored modules by modifying my <code>pylintrc</code> file, in the <code>[TYPECHECK]</code> section:

<pre><code>[TYPECHECK]

ignored-modules = numpy
</code></pre>

Depending on the error, you might also need to add the following line (still in the <code>[TYPECHECK] section</code>):

<pre><code>ignored-classes = numpy
</code></pre>

blocks|key|166213|text|在Pylint的最新版本中，可以将--extension-pkg-whitelist=numpy添加到Pylint命令中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|166214|他们在早期版本中以一种不安全的方式修复了这个问题。现在，如果您希望他们更仔细地查看标准库之外的包，则必须显式地将其列入白名单。See+here。|166215|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/PyCQA/pylint/issues/397^0|H|V|0|1R|8|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

In recent versions of Pylint you can add <code>--extension-pkg-whitelist=numpy</code> to your Pylint command.
They had fixed this problem in an earlier version in an unsafe way. Now if you want them to look more carefully at a package outside of the standard library, you must explicitly whitelist it. <a href="https://github.com/PyCQA/pylint/issues/397" rel="nofollow noreferrer">See here</a>.

blocks|key|166217|text|这似乎至少在Pylint+1.1.0中是有效的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166218|[TYPECHECK]

ignored-classes=numpy|code-block|syntax|javascript|166219|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 seems to work in at least Pylint 1.1.0:
<pre><code>[TYPECHECK]

ignored-classes=numpy
</code></pre>

blocks|key|2765962|text|我在一个正在处理的小型NumPy项目中遇到了同样的错误，并决定忽略NumPy模块就可以了。我创建了一个包含以下内容的.pylintrc文件：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2765963|$+pylint+--generate-rcfile+>+~/.pylintrc|2765964|遵循paduwan's和j_houg's的建议，我修改了以下部分：|2765965|[MASTER]

#+A+comma-separated+list+of+package+or+module+names+from+where+C+extensions+may
#+be+loaded.+Extensions+are+loading+into+the+active+Python+interpreter+and+may
#+run+arbitrary+code
extension-pkg-whitelist=numpy|code-block|syntax|javascript|2765966|和|2765967|[TYPECHECK]

#+List+of+module+names+for+which+member+attributes+should+not+be+checked
#+(useful+for+modules/projects+where+namespaces+are+manipulated+during+runtime
#+and+thus+existing+member+attributes+cannot+be+deduced+by+static+analysis.+It
#+supports+qualified+module+names,+as+well+as+Unix+pattern+matching.
ignored-modules=numpy

#+List+of+classes+names+for+which+member+attributes+should+not+be+checked
#+(useful+for+classes+with+attributes+dynamically+set).+This+supports+can+work
#+with+qualified+names.
ignored-classes=numpy|2765968|它“修复”了我的问题。|2765969|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/20553551/how-do-i-get-pylint-to-recognize-numpy-members/27943375#27943375|1|https://stackoverflow.com/questions/20553551/how-do-i-get-pylint-to-recognize-numpy-members/31465070#31465070^0|1M|9|0|0|14|0|2|9|0|C|8|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@$9|1B|A|1C|1|1D]|$9|1E|A|1F|1|1G]]|E|$]]|$1|J|3|K|5|L|7|1H|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1I|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1J|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|1K|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]]]

I was getting the same error for a small NumPy project I was working on and decided that ignoring the NumPy modules would do just fine. I created a <code>.pylintrc</code> file with:
<code>$ pylint --generate-rcfile &gt; ~/.pylintrc</code>
And following <a href="https://stackoverflow.com/questions/20553551/how-do-i-get-pylint-to-recognize-numpy-members/27943375#27943375">paduwan's</a> and <a href="https://stackoverflow.com/questions/20553551/how-do-i-get-pylint-to-recognize-numpy-members/31465070#31465070">j_houg's</a> advice I modified the following sectors:
<pre class="lang-bash prettyprint-override"><code>[MASTER]

# A comma-separated list of package or module names from where C extensions may
# be loaded. Extensions are loading into the active Python interpreter and may
# run arbitrary code
extension-pkg-whitelist=numpy
</code></pre>
and
<pre><code>[TYPECHECK]

# List of module names for which member attributes should not be checked
# (useful for modules/projects where namespaces are manipulated during runtime
# and thus existing member attributes cannot be deduced by static analysis. It
# supports qualified module names, as well as Unix pattern matching.
ignored-modules=numpy

# List of classes names for which member attributes should not be checked
# (useful for classes with attributes dynamically set). This supports can work
# with qualified names.
ignored-classes=numpy
</code></pre>
and it &quot;fixed&quot; my issue.

blocks|key|2978857|text|作为j_hougs+answer的扩展，您现在可以在.pylintrc中将有问题的模块添加到该行中，它在生成时已经准备为空：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2978858|extension-pkg-whitelist=numpy|code-block|syntax|javascript|2978859|您可以通过执行以下操作来生成示例.pylintrc：|2978860|pylint+--generate-rcfile+>+.pylintrc|2978861|然后编辑提到的行。|2978862|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/20553551/how-do-i-get-pylint-to-recognize-numpy-members/31465070#31465070^0|2|E|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

In extension to <a href="https://stackoverflow.com/questions/20553551/how-do-i-get-pylint-to-recognize-numpy-members/31465070#31465070">j_hougs answer</a>, you can now add the modules in question to this line in .pylintrc, which is already prepared empty on generation:
<pre><code>extension-pkg-whitelist=numpy
</code></pre>
You can generate a sample .pylintrc by doing:
<pre><code>pylint --generate-rcfile &gt; .pylintrc
</code></pre>
And then edit the mentioned line.

blocks|key|170045|text|如果将Visual+Studio+Code与Don+Jayamanne的优秀Python+extension一起使用，请将用户设置添加到白名单NumPy：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|170046|{
++++//+Whitelist+NumPy+to+remove+lint+errors
++++"python.linting.pylintArgs":+[
++++++++"--extension-pkg-whitelist=numpy"
++++]
}|code-block|syntax|javascript|170047|entityMap|0|LINK|mutability|MUTABLE|url|https://code.visualstudio.com/|1|http://donjayamanne.github.io/pythonVSCode^0|3|I|0|12|G|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

If using <a href="https://code.visualstudio.com/" rel="noreferrer">Visual Studio Code</a> with Don Jayamanne's excellent <a href="http://donjayamanne.github.io/pythonVSCode" rel="noreferrer">Python extension</a>, add a user setting to whitelist NumPy:
<pre><code>{
 // Whitelist NumPy to remove lint errors
 &quot;python.linting.pylintArgs&quot;: [
 &quot;--extension-pkg-whitelist=numpy&quot;
 ]
}
</code></pre>

blocks|key|166289|text|从前面的答案中复制粘贴一点，以总结工作情况(至少对我来说是这样：Debian 8|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|166290|166291|在某些旧版本的Pylint中，存在一个问题，使其无法与NumPy+(以及其他类似的软件包)一起使用。|ordered-list-item|166292|166293|166294|现在问题已经解决，但出于安全原因，默认情况下禁用外部C包(C代码-like+NumPy-的Python接口)。|166295|166296|您可以创建一个白名单，以允许在文件~/.pylintrc.中使用它们。|style|CODE|166297|运行的基本命令：|166298|#+ONLY+if+you+do+not+already+have+a+.pylintrc+file+in+your+home
$+pylint+--generate-rcfile+>+.pylintrc|code-block|syntax|javascript|166299|然后打开文件，在extension-pkg-whitelist=后面添加你想要的包，用逗号隔开。您可以在命令行中使用选项--extension-pkg-whitelist=numpy来实现相同的行为。|166300|如果忽略[TYPECHECK]部分中的一些包，这意味着Pylint永远不会显示与这些包相关的错误。实际上，Pylint不会告诉您有关这些包的任何信息。|166301|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Debian_version_history#Debian_8_(Jessie%2529)%2520(Jessie)^0|W|8|0|0|0|0|0|0|0|0|H|B|0|0|0|8|O|1O|V|0|4|B|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@$A|1A|B|1B|1|1C]]|C|$]]|$1|D|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1E|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]|$1|J|3|K|5|G|7|1H|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1J|8|@$A|1K|B|1L|O|P]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1M|8|@]|9|@]|C|$]]|$1|S|3|T|5|U|7|1N|8|@]|9|@]|C|$V|W]]|$1|X|3|Y|5|6|7|1O|8|@$A|1P|B|1Q|O|P]|$A|1R|B|1S|O|P]]|9|@]|C|$]]|$1|Z|3|10|5|6|7|1T|8|@$A|1U|B|1V|O|P]]|9|@]|C|$]]|$1|11|3|-4|5|6|7|1W|8|@]|9|@]|C|$]]]|12|$13|$5|14|15|16|C|$17|18]]]]

A little bit of copy paste from the previous answer to summarize what is working (at least for me: <a href="https://en.wikipedia.org/wiki/Debian_version_history#Debian_8_(Jessie)" rel="nofollow noreferrer">Debian 8</a> (Jessie))
<ol>
<li>In some older version of Pylint there was a problem preventing it working with NumPy (and other similar packages).
</li>
<li>Now that problem has been solved, but external C packages (Python interfaces to C code -like NumPy-) are disabled by default for security reasons.
</li>
<li>You can create a white list, to allow Pylint to use them in the file <code>~/.pylintrc</code>.
</li>
</ol>
Basic command to run:
<pre><code># ONLY if you do not already have a .pylintrc file in your home
$ pylint --generate-rcfile &gt; .pylintrc
</code></pre>
Then open the file and add the packages you want after <code>extension-pkg-whitelist=</code> separated by comma. You can have the same behavior using the option <code>--extension-pkg-whitelist=numpy</code> from the command line.
If you ignore some packages in the <code>[TYPECHECK]</code> section that means that Pylint will never show errors related to those packages. In practice, Pylint will not tell you anything about those packages.

blocks|key|2766051|text|快速回答:将Pylint更新到1.7.1+(如果您使用Conda，请使用conda-forge提供的Pylint+1.7.1。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2766052|我在Pylint+GitHub+here中发现了类似的问题，有人回复说，在更新到1.7.1之后，一切都正常了。|2766053|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Conda_(package_manager%2529)%2520to%2520manage%2520packages|1|https://github.com/PyCQA/pylint/issues/1161^0|R|5|0|0|2|I|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

A quick answer: update Pylint to 1.7.1 (use conda-forge provided Pylint 1.7.1 if you use <a href="https://en.wikipedia.org/wiki/Conda_(package_manager)" rel="nofollow noreferrer">Conda</a> to manage packages).
I found a similar issue in <a href="https://github.com/PyCQA/pylint/issues/1161" rel="nofollow noreferrer">Pylint GitHub here</a> and someone replied everything getting OK after updating to 1.7.1.

blocks|key|167433|text|为了忽略numpy.core属性产生的所有错误，我们现在可以使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|167434|$+pylint+a.py+--generated-members=numpy.*|code-block|syntax|javascript|167435|作为另一种解决方案，将此选项添加到~/.pylintrc或/etc/pylintrc文件：|offset|length|style|BOLD|167436|[TYPECHECK]

#+List+of+members+which+are+set+dynamically+and+missed+by+pylint+inference
#+system,+and+so+shouldn't+trigger+E1101+when+accessed.+Python+regular
#+expressions+are+accepted.
generated-members=numpy.*|167437|此feature是在PyLint+1.6.0中引入的。应该注意的是，原始问题的代码片段通过了这个版本的linting，即使没有任何额外的设置。但是，这在更复杂的情况下很有用。|167438|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.pylint.org/en/1.6.0/whatsnew/1.6.html#new-features^0|0|0|H|B|T|D|0|0|1|7|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]|$I|13|J|14|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|16|8|@]|9|@$I|17|J|18|1|19]]|A|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

For ignoring all the errors generated by numpy.core‘s attributes, we can now use:
<pre><code>$ pylint a.py --generated-members=numpy.*
</code></pre>
As another solution, add this option to ~/.pylintrc or /etc/pylintrc file:
<pre><code>[TYPECHECK]

# List of members which are set dynamically and missed by pylint inference
# system, and so shouldn't trigger E1101 when accessed. Python regular
# expressions are accepted.
generated-members=numpy.*
</code></pre>
This <a href="https://docs.pylint.org/en/1.6.0/whatsnew/1.6.html#new-features" rel="nofollow noreferrer">feature</a> was introduced in PyLint 1.6.0. It should be noted that code snippet from original question passed linting with this version even without any additional settings. However, this is useful in more complex cases.

blocks|key|170080|text|我不确定这是否是一个解决方案，但在Visual+Studio代码中，一旦我在用户设置中显式编写启用Pylint，所有模块都可以识别。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|170081|{
++++"python.linting.pep8Enabled":+true,
++++"python.linting.pylintEnabled":+true
}|code-block|syntax|javascript|170082|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|$]]

I'm not sure if this is a solution, but in Visual Studio Code once I wrote explicitly in my user settings to enable Pylint, all modules were recognized.
<pre><code>{
 &quot;python.linting.pep8Enabled&quot;: true,
 &quot;python.linting.pylintEnabled&quot;: true
}
</code></pre>

blocks|key|2978938|text|这个问题最终在Pylint+1.8.2中得到了解决。它开箱即用，并且不需要对pylintrc进行调整！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2978939|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|$]]

This has finally been resolved in Pylint 1.8.2. It works out of the box, and pylintrc tweaks aren't needed!

blocks|key|168431|text|这个解决方案对我很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|168432|基本上，从左下角选择齿轮图标Setting→Workspace+Setting→Extension→Python+Configuration→点击任意扩展列表在文件"python.linting.pylintArgs“中添加以下内容：”--+Settings.json+-pkg-→→=→“|168433|我使用的是Visual+Studio+Code+1.27.2。|offset|length|168434|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Visual_Studio_Code^0|0|0|5|I|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

This solution worked for me.
Basically, go to select the gear icon from the bottom left → Setting → Workspace Setting → Extension → Python Configuration → click on any Settings.json → add this in the file
&quot;python.linting.pylintArgs&quot; : [ &quot;--extension-pkg-whitelist=numpy&quot; ]
I am using <a href="https://en.wikipedia.org/wiki/Visual_Studio_Code" rel="nofollow noreferrer">Visual Studio Code</a> 1.27.2.

blocks|key|168436|text|如果您不想添加更多配置，请将此代码添加到您的配置文件中，而不是添加“白名单”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|168437|{
++++"python.linting.pylintArgs":+["--generate-members"],
}|code-block|syntax|javascript|168438|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|$]]

If you don't want to add more configuration, please add this code to your configuration file, instead of 'whitelist'.
<pre class="lang-json prettyprint-override"><code>{
 &quot;python.linting.pylintArgs&quot;: [&quot;--generate-members&quot;],
}
</code></pre>

blocks|key|170104|text|最近(自从Spyder或Pylint或?中的一些变化)，我从Spyder对astropy.constants符号的静态代码分析中得到了E1101错误(“没有成员”)。我不知道为什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|170105|对于Linux或Unix系统(Mac可能类似)上的所有用户，我的简单解决方案是创建一个/etc/pylintrc文件，如下所示：|170106|[TYPECHECK]
ignored-modules=astropy.constants|code-block|syntax|javascript|170107|当然，这也可以放在一个个人的$HOME/.pylintrc文件中。而且，我可以更新一个现有的文件。|170108|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Spyder_%2528software%2529^0|5|6|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

Lately (since something changed in <a href="https://en.wikipedia.org/wiki/Spyder_%28software%29" rel="nofollow noreferrer">Spyder</a> or Pylint or ?), I have been getting E1101 errors (&quot;no member&quot;) from Spyder's static code analysis on astropy.constants symbols. I don't have any idea why.
My simplistic solution for all users on a Linux or Unix system (Mac is probably similar) is to create an /etc/pylintrc file as follows:
<pre><code>[TYPECHECK]
ignored-modules=astropy.constants
</code></pre>
Of course, this could, instead, be put in a personal $HOME/.pylintrc file. And, I could have updated an existing file.

blocks|key|2978997|text|我用一个不同的模块(kivy.properties)也遇到了同样的问题，它是一个包装的C模块，比如NumPy。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2978998|使用Visual+Studio+Code+V1.38.0，接受的解决方案停止了项目的所有linting。因此，虽然它确实移除了假阳性no-name-in-module，但它并没有真正改善这种情况。|2978999|对我来说，最好的变通方法是在有问题的模块上使用--ignored-modules参数。问题是，通过python.linting.pylintArgs传递任何参数都会清除default+Visual+Studio+Code+settings，因此您还需要重置这些参数。这给我留下了以下settings.json文件：|2979000|{
++++"python.pythonPath":+"C:\\Python\\Python37\\python.exe",
++++"python.linting.pylintEnabled":+true,
++++"python.linting.enabled":+true,
++++"python.linting.pylintArgs":+[
++++++++"--ignored-modules=kivy.properties",
++++++++"--disable=all",
++++++++"--enable=F,E,unreachable,duplicate-key,unnecessary-semicolon,global-variable-not-assigned,unused-variable,binary-op-exception,bad-format-string,anomalous-backslash-in-string,bad-open-mode"
++++]
}|code-block|syntax|javascript|2979001|entityMap|0|LINK|mutability|MUTABLE|url|https://code.visualstudio.com/docs/python/linting#_pylint^0|A|F|0|1U|H|0|N|H|1D|P|2C|Z|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|J|3|K|5|L|7|1A|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

I had the same problem with a different module (<code>kivy.properties</code>) which is a wrapped C module like NumPy.
Using Visual Studio Code V1.38.0, the accepted solution stopped all linting for the project. So, while it did indeed remove the false-positive <code>no-name-in-module</code>, it didn't really improve the situation.
The best workaround for me was to use the <code>--ignored-modules</code> argument on the offending module. The trouble is, passing any argument via <code>python.linting.pylintArgs</code> wipes out the <a href="https://code.visualstudio.com/docs/python/linting#_pylint" rel="nofollow noreferrer">default Visual Studio Code settings</a>, so you need to reset those also. That left me with the following settings.json file:
<pre><code>{
 &quot;python.pythonPath&quot;: &quot;C:\\Python\\Python37\\python.exe&quot;,
 &quot;python.linting.pylintEnabled&quot;: true,
 &quot;python.linting.enabled&quot;: true,
 &quot;python.linting.pylintArgs&quot;: [
 &quot;--ignored-modules=kivy.properties&quot;,
 &quot;--disable=all&quot;,
 &quot;--enable=F,E,unreachable,duplicate-key,unnecessary-semicolon,global-variable-not-assigned,unused-variable,binary-op-exception,bad-format-string,anomalous-backslash-in-string,bad-open-mode&quot;
 ]
}
</code></pre>

blocks|key|2979016|text|这是generated-members.的一个老bug如果使用numpy之外的其他名称，如np或foo，则必须将其添加到Pylint配置中(空格或逗号分隔-没关系)，因为Pylint无法识别这一点。所以它应该看起来像这样：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2979017|[pylint]
generated-members=numpy.*,np.*,foo.*|code-block|syntax|javascript|2979018|它甚至在无成员错误中抛出完整路径，但表达式需要准确。这是一个老的bug，似乎很快就会被修复。检查Issue+#2498+in+logilab/pylint。|2979019|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/PyCQA/pylint/issues/2498^0|2|H|V|5|19|2|1C|3|0|0|1C|T|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|M|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

It's an old bug with generated-members. If you use another name than numpy, like np or foo, then you must add it in the Pylint configuration (space or comma-separated - no matter), because Pylint doesn't recognize that. So it should look like this:
<pre><code>[pylint]
generated-members=numpy.*,np.*,foo.*
</code></pre>
It even throws a full path in no-member error, but the expression needs to be exact. It's an old bug and seems to be fixed soon. Check <a href="https://github.com/PyCQA/pylint/issues/2498" rel="nofollow noreferrer">Issue #2498 in logilab/pylint</a>.

I am running Pylint on a Python project. Pylint makes many complaints about being unable to find NumPy members. How can I avoid this while avoiding skipping membership checks?
From the code:
<pre><code>import numpy as np

print np.zeros([1, 4])
</code></pre>
Which, when ran, I get the expected:
<blockquote>
[[ 0. 0. 0. 0.]]
</blockquote>
However, Pylint gives me this error:
<blockquote>
E: 3, 6: Module 'numpy' has no 'zeros' member (no-member)
</blockquote>
For versions, I am using Pylint 1.0.0 (astroid 1.0.1, common 0.60.0) and trying to work with NumPy 1.8.0.

How do I get Pylint to recognize NumPy members?

静态代码分析

Visual Studio

Python

Ubuntu

Linux

Unix

我正在Python项目上运行Pylint。Pylint多次抱怨找不到NumPy成员。我如何避免这种情况，同时避免跳过成员资格检查？从代码中：import numpy as npprint np.zeros([1, 4])当运行时，我得到了预期的结果： [ 0.0。0。0。]然而，Pylint给了我这个错误： E: 3，...

问如何让Pylint识别NumPy成员？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让Pylint识别NumPy成员？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让Pylint识别NumPy成员？
EN