You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VS Code version: 1.15
Python Extension version: 0.7
Python Version: 3.6
OS and version: win10
Actual behavior
I created 2 files: a.py and b.py.
b.py:
defSpeak(self, id):
pass
a.py:
importbc1=1# type: bc2: b=1
In a.py file, the pythonVSCode plugin can not identify c1, and there are no intellisense for c1. But the pythonVSCode plugin can identify c2, there are intellisense information for c2.
Copied from original issue: DonJayamanne/pythonVSCode#1223
I tried this in the latest master and the result I'm getting is that c1 is completed as an int (No support for PEP 484 type comments), c2 is not completed at all, and b is completed as an int!
Unless this extension does something to alter Jedi's behavior. This feels like a bug in Jedi (Jedi is supposed to handle [PEP 526](https://www.python.org/dev/peps/pep-0526/ but it seems to handle it wrong) and should probably be submitted as an issue upstream to Jedi.
Activity
MikhailArkhipov commentedon Feb 12, 2018
With jedi 0.11.1 it seems to be OK.
#674
segevfiner commentedon Feb 12, 2018
I think the issue is with auto completing for c1 not for b. I don't think Jedi knows about pep 484 type comments. See davidhalter/jedi#946
MikhailArkhipov commentedon Feb 13, 2018
6015468
segevfiner commentedon Feb 15, 2018
I tried this in the latest master and the result I'm getting is that
c1is completed as anint(No support for PEP 484 type comments),c2is not completed at all, andbis completed as anint!Unless this extension does something to alter Jedi's behavior. This feels like a bug in Jedi (Jedi is supposed to handle [PEP 526](https://www.python.org/dev/peps/pep-0526/ but it seems to handle it wrong) and should probably be submitted as an issue upstream to Jedi.
zhoudotnet commentedon May 17, 2018
What's the current progress for this ticket?
brettcannon commentedon May 17, 2018
zhoudotnet we closed it because we believed it was resolved with the latest release of Jedi. If you are having issues then please open a a new issue.