Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Return type not showing on Intellisense #185

Closed
DonJayamanne opened this issue Nov 14, 2017 · 5 comments
Closed

Return type not showing on Intellisense #185

DonJayamanne opened this issue Nov 14, 2017 · 5 comments
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug

Comments

@DonJayamanne
Copy link

From @alchermd on September 23, 2017 13:38

Environment data

VS Code version: 1.16.1
Python Extension version: 0.7.0
Python Version: 3.5
OS and version: Linux Mint 18.2

Actual behavior

The -> str part is not shown as defined in the function prototype baz at module bar.

Expected behavior

Shouldn't it work the same way as above? Or I'm missing something obvious about type hinting? 😄

Copied from original issue: DonJayamanne/pythonVSCode#1234
@brettcannon brettcannon added awaiting 1-verification area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug labels Nov 14, 2017
@brettcannon brettcannon self-assigned this Jan 11, 2018
@MikhailArkhipov
Copy link

davidhalter/jedi#990

@MikhailArkhipov MikhailArkhipov removed their assignment Feb 12, 2018
@gustavovalverde gustavovalverde mentioned this issue Feb 26, 2018
Closed
15 tasks
@brettcannon brettcannon mentioned this issue Apr 19, 2018
Closed
@austinbutler
Copy link

Is this basically waiting on davidhalter/jedi#780 now?

@brettcannon
Copy link
Member

@austinbutler not sure. I was suggest you give the language server a try by setting "python.jediEnabled": false and see if that solves your issue.

@austinbutler
Copy link

@brettcannon the prompt to switch from Jedi to the MS Python server showed up for me a day or two ago and since then it does appear. Thanks!

@brettcannon
Copy link
Member

Closing as this is an upstream issue which we don't have direct control or influence over.

@ghost ghost removed the needs upstream fix label Jul 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Aug 5, 2019
NextLight added a commit to NextLight/vscode-python that referenced this issue Feb 17, 2020
@NextLight
Use correct jedi function to generate signatures.
d540965 
This properly fixes microsoft#185 since it now shows the return type as expected.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@brettcannon @austinbutler @DonJayamanne @MikhailArkhipov