cv2 module members are not recognized #2426

uriva · 2018-08-20T12:28:37Z

When importing cv2 I get errors such as:

[pylint] E1101:Module 'cv2' has no 'imread' member
[pylint] E1101:Module 'cv2' has no 'resize' member
[pylint] E1101:Module 'cv2' has no 'imshow' member
[pylint] E1101:Module 'cv2' has no 'waitKey' member
[pylint] E1101:Module 'cv2' has no 'destroyAllWindows' member

etc'

(the code itself runs fine)

I'm using VSCode 1.26.1 and Python 3.6.5.

See this issue for more complaints: https://github.com/DonJayamanne/pythonVSCode/issues/623

PCManticore · 2018-08-21T06:12:22Z

This should work if you pass --extension-pkg-whitelist=cv2 to pylint as in pylint --extension-pkg-whitelist=cv2 .... The reason for this is that cv2 seems to be an extension package, thus it's C code that pylint cannot understand. The extension whitelist flag lets pylint import cv2 in order to build an AST out of the imported cv2 module.

uriva · 2018-08-21T07:02:20Z

To future readers, in vsc this means adding this line to the settings:
"python.linting.pylintArgs": ["--extension-pkg-whitelist=cv2"]

cipri-tom · 2018-09-12T15:57:07Z

Thanks @PCManticore

However, even with the extension enables, pylint still doesn't recognise 2nd level members, such as cv2.ml.KNearest_create() or cv2.ximgproc.thinning().

I believe it is the same case as #779 ?

cipri-tom · 2018-12-05T22:58:15Z

@ashraf-minhaj use the Cmd+shift+p shortcut (or ctrl instead of cmd) and type "open settings (json)". There should be an option which opens the json settings and you can add the line there

Davidnet · 2019-01-12T11:07:45Z

I'm encountering the same situation:

dgromov@Predator-G3-571 ~/D/u/s/p/CarND-Advanced-Lane-Lines> pylint camera_calibration.py --extension-pkg-whitelist=cv2 | tail                                                                                                       (SDCND) 
camera_calibration.py:157:18: E1101: Module 'cv2' has no 'undistort' member (no-member)
camera_calibration.py:159:12: E1101: Module 'cv2' has no 'imshow' member (no-member)
camera_calibration.py:160:12: E1101: Module 'cv2' has no 'waitKey' member (no-member)
camera_calibration.py:162:12: E1101: Module 'cv2' has no 'imwrite' member (no-member)
camera_calibration.py:163:12: E1101: Module 'cv2' has no 'destroyAllWindows' member (no-member)
camera_calibration.py:129:0: R1711: Useless return at end of function or method (useless-return)

----------------------------------------------------------------------
Your code has been rated at -12.67/10 (previous run: -12.67/10, +0.00)

dgromov@Predator-G3-571 ~/D/u/s/p/CarND-Advanced-Lane-Lines> conda list | grep  "pylint\|astroid"                                                                                                                                    (SDCND) 
astroid                   2.1.0                    py36_0  
pylint                    2.2.2                    py36_0

PCManticore · 2019-01-13T13:51:43Z

As mentioned, most of the errors should be already solved by using --extension-pkg-whitelist=cv2. But unfortunately, as @cipri-tom mentioned, there are a couple of cv2 modules for which that flag does not work. I think the best way forward is for someone to propose a patch to astroid, the library that pylint uses for infererence, to add support for cv2 in a similar fashion to how we added for numpy in #779. Unfortunately we're not familiar with cv2 so it's not something that we'd do ourselves.

mehdimammadov · 2019-03-26T14:53:02Z

https://www.bilibili.com/video/av33693850/
"python.linting.pylintArgs": ["--generate-members"]

satyajithj · 2019-05-03T13:01:39Z

For me, pylint cannot process cv2 when I build cv2 from source. Works when installed using pip.

yeknafar · 2019-06-09T20:37:14Z

@mehanton this works for me.

Thank you. :)

LintangWisesa · 2019-06-13T02:37:49Z

On VScode: CTRL + Shift + P
Choose "Preferences: Open Settings (JSON)"
Add this line into JSON file:
"python.linting.pylintArgs": ["--generate-members"]
Done, it works for me 👍

githarshp · 2019-07-04T16:02:04Z

On VScode: CTRL + Shift + P

Choose "Preferences: Open Settings (JSON)"

Add this line into JSON file:
"python.linting.pylintArgs": ["--generate-members"]

Done, it works for me 👍

Thanks, man! it worked for me too

nyck33 · 2019-07-23T03:44:40Z

on VSCode Ubuntu I did "python.linting.pylintArgs": ["--generate-members", "--extension-pkg-whitelist=cv2"] which worked.

insung3511 · 2019-07-28T00:27:30Z

On VScode: CTRL + Shift + P

Choose "Preferences: Open Settings (JSON)"

Add this line into JSON file:
"python.linting.pylintArgs": ["--generate-members"]

Done, it works for me 👍

Hm.... I can't edit "defaultSetting.json file....

LintangWisesa · 2019-07-28T03:07:18Z

On VScode: CTRL + Shift + P

Choose "Preferences: Open Settings (JSON)"

Add this line into JSON file:
"python.linting.pylintArgs": ["--generate-members"]

Done, it works for me 👍

Hm.... I can't edit "defaultSetting.json file....

@insung3511 It must be "settings.json", not "defaultSetting.json"! Make sure you choose "Preferences: Open Settings (JSON)", not "Preferences: Open Default Settings (JSON)" 👌

duttanaman1 · 2019-07-31T17:06:10Z

thanks

funny860 · 2019-08-13T13:12:48Z

thanks for the help guys

Blinue · 2019-08-21T03:22:46Z

The "--generate-members" option is wrong!
It works because pylint fails.
The command "pylint --generate-members test.py" fails because of "no such option: --generate-members".

Blinue · 2019-08-21T03:49:15Z

Look at this, but the solution mentioned here won't work either.
It seems that the only solution is to disable the "no-member" error.

rivergold · 2019-10-14T07:53:22Z

The "python.linting.pylintArgs": ["--generate-members"] is wrong, it will make pylint not work.
The correct way is to set ""python.linting.pylintArgs": ["--generated-members=cv2.*"] which only config for cv2, reference @bjtho08 reply in #779.

t31060 · 2020-03-06T06:25:44Z

i compiled opencv from soruce and passed the args to pylitn but still intellisense doesnt work, there is another way to solve?

Saksham2dubey · 2020-03-26T14:27:16Z

I also facing the same problem of "cv2 module members are not recognized
"
what I did was
after importing cv2
write:
from cv2 import cv2
this worked for me because my JSON is not amendable

JulianToledano · 2020-04-17T17:59:51Z

On VScode: CTRL + Shift + P

Choose "Preferences: Open Settings (JSON)"

Add this line into JSON file:
"python.linting.pylintArgs": ["--generate-members"]

Done, it works for me +1

Hm.... I can't edit "defaultSetting.json file....

Now my pylint just don't show any erros 😅

JulianToledano · 2020-04-17T18:04:47Z

The "python.linting.pylintArgs": ["--generate-members"] is wrong, it will make pylint not work.
The correct way is to set ""python.linting.pylintArgs": ["--generated-members=cv2.*"] which only config for cv2, reference @bjtho08 reply in #779.

Thanks that solves it.

On VScode: CTRL + Shift + P
Choose "Preferences: Open Settings (JSON)"
Add this line into JSON file: "python.linting.pylintArgs": ["--generated-members=cv2.*"]
Done, it works for me +1

Vivraan · 2020-08-07T05:21:19Z

@Shinit5201

blackhawk005 · 2020-08-07T06:00:27Z

Thanks

…

On 07-Aug-2020, at 10:51 AM, Shivam Mukherjee ***@***.***> wrote: @Shinit5201 <https://github.com/Shinit5201> <https://user-images.githubusercontent.com/12777564/89611882-ea42d380-d89b-11ea-959c-92d43a821240.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2426 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APVLRH3TAOJMCQRBJZ5VC33R7OFN3ANCNFSM4FQPTXBA>.

kshitij-agarwal · 2020-09-04T06:52:24Z

After reading such complex tasks, I was totally surprised.

A very simple way is:
Instead of import cv2 import from cv2 import cv2

It works like a charm.

Vivraan · 2020-09-04T07:00:35Z

After reading such complex tasks, I was totally surprised.

A very simple way is:
Instead of import cv2 import from cv2 import cv2

It works like a charm.

You could also take a step further and import even more granularly into individual classes or features instead of the whole module!

kritikaparmar-programmer · 2020-09-08T19:12:39Z

After reading such complex tasks, I was totally surprised.

A very simple way is:
Instead of import cv2 import from cv2 import cv2

It works like a charm.

It worked dude!!😁

For cv2 reference: pylint-dev/pylint#2426 Signed-off-by: Ashish Saini <sainiashish08@gmail.com>

slugb0t · 2020-09-26T23:44:46Z

After reading such complex tasks, I was totally surprised.

A very simple way is:
Instead of import cv2 import from cv2 import cv2

It works like a charm.

a simple solution wow thank you

zchrissirhcz · 2020-09-28T11:42:35Z

"python.linting.pylintArgs": ["--generate-members"] works for me.

Btw, tts 2020-09-28 already, why people still have to setup this stuff for pylint?

bthorsted · 2020-09-28T12:30:15Z

"python.linting.pylintArgs": ["--generate-members"] works for me.

Btw, tts 2020-09-28 already, why people still have to setup this stuff for pylint?

That argument is wrong and will make pylint fail silently. See the comments earlier in the thread for an explanation.

jofrev · 2020-10-11T09:58:22Z

After reading such complex tasks, I was totally surprised.

A very simple way is:
Instead of import cv2 import from cv2 import cv2

It works like a charm.

It won't report an error in VS Code's problems tab any longer that's true. But if you run pylint from your terminal you'll still get

I1101: Module 'cv2.cv2' has no 'imread' member, but source is unavailable. Consider adding this module to extension-pkg-whitelist if you want to perform analysis based on run-time introspection of living objects. (c-extension-no-member)

with from cv2 import cv2 instead of

E1101: Module 'cv2' has no 'imread' member (no-member)

with import cv2. Depending on how one intends to use pylint, whitelisting cv2 in pylint settings as described numerous times above may actually be better.

gautamjain1009 · 2020-10-14T11:08:01Z

@Shinit5201

this is not working for me I am using Opencv 4.1.0 build from source in an anaconda environment.

Mechazo11 · 2020-11-28T05:03:36Z

On VScode: CTRL + Shift + P

Choose "Preferences: Open Settings (JSON)"

Add this line into JSON file:
"python.linting.pylintArgs": ["--generate-members"]

Done, it works for me 👍

Worked for me too. Thanks

ardf · 2021-04-29T08:56:31Z

I also facing the same problem of "cv2 module members are not recognized
"
what I did was
after importing cv2
write:
from cv2 import cv2
this worked for me because my JSON is not amendable

Thanks! worked for me too

nnmrts · 2021-09-05T08:39:28Z

I can't believe how many people here are recommending to edit the clumsy vscode setting "python.linting.pylintArgs".

Not only is it just solving the issue locally, especially when you edit your global vscode settings.json, it also overrides any settings from a .pylintrc file, which is not immediately obvious. Using vscode's settings to add command line arguments to some binary running in the background is a bad idea in general, and should only be done as a last resort.

What you should really do, in my opinion, is to generate a pylint configuration file inside your project folder like this:

pylint --generate-rcfile > .pylintrc

and then edit the settings extension-pkg-allow-list and generated-members there.

You can of course also edit these settings in your user- or system-wide .pylintrc, I'd advise against that though.

domajstorovic · 2021-11-12T22:56:24Z

I can't believe how many people here are recommending to edit the clumsy vscode setting "python.linting.pylintArgs".

Not only is it just solving the issue locally, especially when you edit your global vscode settings.json, it also overrides any settings from a .pylintrc file, which is not immediately obvious. Using vscode's settings to add command line arguments to some binary running in the background is a bad idea in general, and should only be done as a last resort.

What you should really do, in my opinion, is to generate a pylint configuration file inside your project folder like this:
pylint --generate-rcfile > .pylintrc
and then edit the settings extension-pkg-allow-list and generated-members there.

You can of course also edit these settings in your user- or system-wide .pylintrc, I'd advise against that though.

This. By far the most elegant solution. Thanks!

KukavicaHome · 2022-02-19T18:05:56Z

VS2019 works for me.

I read [1], [2] and then tried this... [1] pylint-dev/pylint#3437 [2] pylint-dev/pylint#2426 Interesting [3] seems to recommend what we used to do `from cv2 import cv2` or somesuch... [3] pylint-dev/pylint#2426 (comment)

qngv · 2022-07-14T02:50:06Z

install opencv_headless and it works for me.

pylint-dev/pylint#2426 (comment)

ZhiliangWu · 2023-04-23T09:02:09Z

For pyproject.toml file, add the following

[tool.pylint.typecheck]
generated-members = "cv2.*"

Pierre-Sassoulas · 2023-04-23T10:26:00Z

Note that using genrated-members should be the last solution if nothing else work, because it will disable pylint's check on everything coming from cv2.

knowledgeLover · 2023-07-16T22:42:56Z

pip installation is wrong.

Easiest solution and you do not need to worry about any settings or incorrect changes. Much safer.

pip install opencv-python-headless

Try installing opencv-python-headless python dependency instead of opencv-python. That includes a precompiled binary wheel with no external dependencies (other than numpy), and is intended for headless environments like Docker. This saved almost 700mb in my docker image compared with using the python3-opencv Debian package (with all its dependencies).

The package documentation discusses this and the related (more expansive) opencv-contrib-python-headless pypi package.

DungGramer · 2023-12-19T04:06:28Z

Update 2023:

  "pylint.args": ["--extension-pkg-whitelist=cv2"]

LambdaScorpii · 2024-06-30T14:55:51Z

Hello There,

since the new release of OpenCV this no longer works. It still throws the no member error, regardless if you put in "--extension-pkg-whitelist=cv2" or --extension-pkg-allow-list=cv2 (as suggested in the official documentation, as "whitelist"seems dprecated). Any suggestion how to make that work?

Generating all members defies the purpose of PyLint in my opinion...

Pierre-Sassoulas · 2024-07-01T04:52:23Z

Could you open a new issue with a reproducer please @LambdaScorpii ? (Edit: Sorry Bad ping my Bad)

SajjadAemmi · 2024-11-04T11:04:01Z

Option 1

Add --generated-members argument when you run pylint command:

pylint --generated-members=cv2.* client.py

Option 2

Run:

pylint --generate-rcfile > .pylintrc

Then open .pylintrc, find generated-members and write:

generated-members="cv2.*"

LambdaScorpii · 2024-11-09T16:01:23Z

hi @SajjadAemmi,

Thanks for the advice. Unfortubnately, this won't work well because, a) you annot configure this in a persistent manner in the pylint extenstion and b) this removes every scope on linting when it starts with cv2 regardless if right or wrong, so kind of defies the point of the whole linting.

ewwink · 2025-01-22T23:01:01Z

this work for me in 2025, in settings search pylint.args then add --generated-members=cv2.*

PCManticore closed this as completed Aug 21, 2018

Flamefire mentioned this issue Nov 20, 2018

import cv2 not detected microsoft/vscode-python#2879

Closed

brettcannon mentioned this issue Nov 20, 2018

cv2 (opencv-python) intellisense not working microsoft/vscode-python#1993

Closed

hippo91 mentioned this issue Dec 21, 2018

"Module 'numpy' has no ... member" error even with extension-pkg-whitelist=numpy set in pylint.rc #779

Closed

GitMatze mentioned this issue Mar 3, 2020

Add parser for Maharashtra, India electricitymaps/electricitymaps-contrib#2256

Merged

747 mentioned this issue Mar 4, 2020

Intellisense (still) not working for cv2 (Anaconda) #3437

Closed

747 mentioned this issue Mar 9, 2020

pylint extension-pkg-whitelist=cv2 not working only when through the extension (Anaconda) microsoft/vscode-python#10444

Closed

meashishsaini added a commit to meashishsaini/up_scholarship that referenced this issue Sep 19, 2020

Fix some pytlint issues

a6d54a5

For cv2 reference: pylint-dev/pylint#2426 Signed-off-by: Ashish Saini <sainiashish08@gmail.com>

mxochicale mentioned this issue Dec 19, 2022

Remove dependendcy on scikit-surgeryopencvcpp SciKit-Surgery/scikit-surgerycalibration#46

Closed

robertschweizer mentioned this issue Mar 30, 2023

Pylint no-member and no-name-in-module warnings since version 4.6.0.66 opencv/opencv-python#824

Open

4 tasks

bl4ko pushed a commit to bl4ko/ROS that referenced this issue Apr 4, 2023

Fixing cv2 pylint problems

bdce92e

pylint-dev/pylint#2426 (comment)

cv2 module members are not recognized #2426

cv2 module members are not recognized #2426

Comments

uriva commented Aug 20, 2018

PCManticore commented Aug 21, 2018

uriva commented Aug 21, 2018 • edited Loading

cipri-tom commented Sep 12, 2018

cipri-tom commented Dec 5, 2018

Davidnet commented Jan 12, 2019

PCManticore commented Jan 13, 2019

mehdimammadov commented Mar 26, 2019

satyajithj commented May 3, 2019 • edited Loading

yeknafar commented Jun 9, 2019

LintangWisesa commented Jun 13, 2019

githarshp commented Jul 4, 2019

nyck33 commented Jul 23, 2019 • edited Loading

insung3511 commented Jul 28, 2019

LintangWisesa commented Jul 28, 2019

duttanaman1 commented Jul 31, 2019

funny860 commented Aug 13, 2019

Blinue commented Aug 21, 2019

Blinue commented Aug 21, 2019

rivergold commented Oct 14, 2019

t31060 commented Mar 6, 2020

Saksham2dubey commented Mar 26, 2020

JulianToledano commented Apr 17, 2020

JulianToledano commented Apr 17, 2020

Vivraan commented Aug 7, 2020

blackhawk005 commented Aug 7, 2020 via email

kshitij-agarwal commented Sep 4, 2020

Vivraan commented Sep 4, 2020

kritikaparmar-programmer commented Sep 8, 2020

slugb0t commented Sep 26, 2020

zchrissirhcz commented Sep 28, 2020

bthorsted commented Sep 28, 2020

jofrev commented Oct 11, 2020

gautamjain1009 commented Oct 14, 2020

Mechazo11 commented Nov 28, 2020

ardf commented Apr 29, 2021

nnmrts commented Sep 5, 2021

domajstorovic commented Nov 12, 2021

KukavicaHome commented Feb 19, 2022

qngv commented Jul 14, 2022

ZhiliangWu commented Apr 23, 2023

Pierre-Sassoulas commented Apr 23, 2023

knowledgeLover commented Jul 16, 2023 • edited Loading

DungGramer commented Dec 19, 2023

LambdaScorpii commented Jun 30, 2024

Pierre-Sassoulas commented Jul 1, 2024 • edited Loading

SajjadAemmi commented Nov 4, 2024 • edited Loading

Option 1

Option 2

LambdaScorpii commented Nov 9, 2024

ewwink commented Jan 22, 2025

uriva commented Aug 21, 2018 •

edited

Loading

satyajithj commented May 3, 2019 •

edited

Loading

nyck33 commented Jul 23, 2019 •

edited

Loading

knowledgeLover commented Jul 16, 2023 •

edited

Loading

Pierre-Sassoulas commented Jul 1, 2024 •

edited

Loading

SajjadAemmi commented Nov 4, 2024 •

edited

Loading