Activity

1. skvark commented on Oct 13, 2018

   

   skvark

   on Oct 13, 2018

   Member

   More actions

   This seems to be a pylint issue. Add cv2 to the pylint extension package whitelist as suggested by this answer at Stack Overflow: https://stackoverflow.com/a/51916065/5795428

   The wildcard import code in the __init__ file is perfectly valid Python. There's nothing "anti-linter" in the file. The last line is a bit hacky, but as the comment implies, it's needed to expose members which are ignored by the wildcard import.

   I believe that the actual problem is related to the fact that the cv2 is binary extension module. For example Numpy behaves excatly the same way with pylint / vscode: https://stackoverflow.com/questions/20553551/how-do-i-get-pylint-to-recognize-numpy-members
2. skvark

   closed this as completedon Oct 13, 2018
3. kelvinwop commented on Oct 14, 2018

   

   kelvinwop

   on Oct 14, 2018

   Author

   More actions

   Strange. Seems to work with numpy lol.

   Will add this link to the vscode issue