When writing Python code using compiled extensions (the OpenCV Python bindings, for example), PyCharm doesn’t seem to be aware of their availability. The imports are marked with a grey underline, saying “unresolved reference” as a tooltip, and autocomplete doesn’t work, either. (Except for the function names already used in the code.)
This isn’t caused by wrong module paths, the code runs without error when started. Also, after I import the modules in a Python shell, autocomplete starts working as expected.
Is there a solution for that or is this an architectural limitation for compiled extensions? Are there any other IDEs that manage to cope with this problem?
This most probably means that PyCharm can’t see the module you import. In editing mode, PyCharm relies on availability of Python sources of imported modules. If a module is not written in Python but is a C extension module, PyCharm generates a ‘skeleton’ that contains function prototypes, and uses it for completion.
In shell mode, PyCharm uses live imported objects for completion, with slightly different results.
Make sure that your OpenCV installation is visible for the Python interpreter you chose for the project (File / Settings / Python interpreter). If the interpreter is correct, try removing and re-adding it (this is time-consuming a bit, sorry).
If nothing helps, file a bug.