PythonVScode extension doesn`t seem to implement jedi properly - the extension cannot locate the correct symbol definition

[DonJayamanne]

From @circlecrystal on August 28, 2017 4:47

1. In other editors' implementations of jedi can lookup the user defined object, and find the method definition (csv_handle has the writerow() and writerows() methods, and they do show up in some other editor):

2. The vscode python extension implementation of jedi cannot lookup any method which belong to the object of some object of some imported class (label_handle has the writerow() and writerows() methods, but they do not show up in vscode. Instead, vscode show the incorrect methods which don`t actually belong to label_handle object):

(* The imported class in the above and below showcase is with the Python standard library.)

3. The vscode python extension implementation of jedi cannot even lookup any user defined MACRO value (it shows the data type instead, which is pretty much useless for us):

As I also investigated this issue a lot, I found it is not the problem of jedi itself. It is vscode python extension does not use the jedi as correctly as it should.

That`s why we have this problem haunting many of us python programmers who are using this extension right now.

Copied from original issue: DonJayamanne/pythonVSCode#1182

just wants to check on this - does this mean Jedi integration is finally going to be correct? It appears that Jedi autocomplete is still not working appropriately for me at least.

Also, any consideration to using this? https://github.com/palantir/python-language-server

[brettcannon]

All we've done is triaged the issue. No specific plans on addressing this issue have been made yet.

[brettcannon]

@DonJayamanne do you happen to know how we may not be hooking into Jedi fully as suggested by @circlecrystal? I've verified that at least with:

import csv
import io

buf = io.BytesIO()
writer = csv.writer(buf)

doesn't lead to intellisense for writer.