-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opencv-python intellisense is not working under conda #99
Comments
From @njkevlani on July 27, 2017 17:57 |
From @gandhis1 on July 27, 2017 19:20 Can you use the Jedi API to determine whether it is a Jedi issue? |
From @njkevlani on July 27, 2017 19:24 Can you explain it in a better way? @gandhis1 |
From @gandhis1 on July 27, 2017 20:26 Import E.g.
See below for more information: |
From @njkevlani on July 27, 2017 20:45 Here you go: |
From @njkevlani on July 27, 2017 20:47 out put for |
From @fluxin on July 29, 2017 12:25 Same issue here, same completions. |
From @gandhis1 on July 29, 2017 15:33 Since the completions aren't correct that means it's a Jedi issue, no? Post this in that repo. |
From @njkevlani on July 29, 2017 15:49 @gandhis1, in my last post, |
From @wkema on November 5, 2017 6:55 manually setting "jedi path" to the newest release of jedi (0.11.0) locally solves the cv2 problem. But some other features of the extension will be lose like "go to definition" etc. hmmm.... |
I just tested with our latest release and I can get completions for both |
I have exactly the same problem. I have installed opencv using conda and I have jedi with version 0.11.1. |
@ironbar I've re-opened but classified this as potentially a conda-specific issue. |
Meet same issue. cv2 (opencv 3.4) intellisense complied into python3.5 on ubuntu 16.04 did not work at all. |
I am having the same issues as above, where intellisense will not do code completion for opencv. Here is my setup information: VSCode:
OpenCV was built with:
Python Outputs:
*edit: Clarified what code completion does not work |
Installing opencv by: python 2.7.14 |
@anribras @ironbar @denck007 Please test and let me know how it goes. |
The insiders build of the extension works! Code completion for opencv works now! Thank you @DonJayamanne |
+1 the insiders build works |
Thanks guys |
I confirm that it works also for python 2.7 |
Autocompletion works now. Still I met a tip:
[pylint] E1101:Module 'cv2' has no 'Laplacian' member cv2: cv2
and ignored it by adding
"python.linting.pylintArgs": [
"--extension-pkg-whitelist=cv2"
],
in settings and perfect for me. Thank you @don Jayamanne
At 2018-02-27 03:00:30, "Don Jayamanne" <notifications@github.com> wrote:
@anribras@ironbar@denck007
Please could you download the Insiders Build and test this out.
Note: This isn't the insiders build of VS Code, its our dev version of the extension.
It contains a number of fixes related to intellisense, and I'm hoping this resolves the issue you are experiencing.
Please test and let me know how it goes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Insiders build .vsix installed and confirmed working with autocompletion for OpenCV-Python. |
@stevecfloat How long does it take to compile the vscode python extension on your machine? I've in the second task for almost 2 hours. Could you guys provide your .vsix file please? |
@zchrissirhcz it shouldn't take that long. You can always download a development build of the extension. |
From @sarkarstanmoy on April 3, 2017 18:4
Environment data
VS Code version: latest
Python Extension version:
Python Version: 3.5
OS and version: windows 10
Actual behavior
After installing and importing opencv-python package in my project file intellisense is not firing up.
Expected behavior
Steps to reproduce:
Settings
Your launch.json (if dealing with debugger issues):
Your settings.json:
Logs
Output from
Python
output panelOutput from
Console window
(Help->Developer Tools menu)Copied from original issue: DonJayamanne/pythonVSCode#858
The text was updated successfully, but these errors were encountered: