I think solving this problem is not difficult, but I don’t understand why it hasn’t been resolved until now. The following are my proposed solutions to this problem:
types-opencv-python
Generated based on pyopencv_signatures.json from OpenCV documentation build, together with the XML documents generated after the build, my local Python environment, and my patches.
Is there a specific reason causing this issue?
Can I submit a PR for this project based on it?
Due to time constraints, the code’s readability is not very good.
But before submitting the PR, I will fix this issue.
what do you call “bindings”? the actual bindings, or the stubs for an IDE’s library understanding?
what do you consider “incomplete”? specifically? what’s your level of expectation, in general? and in terms of the proper library versus coverage of the contrib repo? what would satisfy your notion of “resolved”?
this is library development work. the forum is not the best place for this. you should take it to opencv’s github. look for existing issues.
I mean this.
I think the IDE should provide suggestions for all the functions and classes mentioned in the OpenCV documentation. For example, the OpenCV documentation mentions that ORB_create can be used in Python, but in the IDE, it should provide parameter hints and return type hints for this function.(Currently, ORB_create has no hints.)
I understand, I will go to GitHub to raise this issue.