-
-
Notifications
You must be signed in to change notification settings - Fork 511
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
Completion not always working with context managers #1084
Comments
sqlite3.connect is a builtin function and it's therefore not that easy to get return types for it. I think your best bet is to wait for #839. In that case we will also try to use https://github.com/python/typeshed which will definitely help you! |
@boojum looks like your "picture" got archived and is no longer visible. Would you perhaps update the description with a summary? |
Sure thing! I'll test it and update the description this weekend. |
It looks like
doesn't work, because there is no way that Jedi knows what If you look at
I guess I'll wait until mypy solves this issue, because I'm pretty sure they also have this issue. |
This was originally reported in davidhalter/jedi#1084.
This was originally reported in davidhalter/jedi#1084.
Problem summary
Completion not always works with context managers. Picture is worth a thousand words:
https://asciinema.org/a/35sDlmrobGcLVHQiUfBOgTaG2
Expected
After the
with
statement I expect the completion to work normally. For example, I expectconn.cursor()
andc.execute()
to start completion afterconn
andc
, respectively. This behaviour occurs withdeoplete-jedi
andipython
completion, both usingjedi
.EDIT: tested against
completor.vim
andjedi-vim
, which produces the same issue.Environment Information
OS:
Neovim version:
Minimal init.vim:
The text was updated successfully, but these errors were encountered: