Skip to content

wrong with auto-complete #5141

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

Closed
benbenji opened this issue Apr 6, 2019 · 3 comments
Closed

wrong with auto-complete #5141

benbenji opened this issue Apr 6, 2019 · 3 comments
Assignees
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug

Comments

@benbenji
Copy link

benbenji commented Apr 6, 2019

Environment data

  • VS Code version: 1.32.3
  • Extension version (available under the Extensions sidebar): 2019.3.6352 (2 April 2019)
  • OS and version: 18.04
  • Python version (& distribution if applicable, e.g. Anaconda): anaconda
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
  • Relevant/affected Python packages and their versions: tensorflow-1.12.0
    There maybe some bug about auto-complete of tensorflow,when I type 'tf.' there are no useful selection appearing,but the last version is ok. moreover, the time analysing code is much longer than the last version.

Expected behaviour

The auto-complete run well when I use tensorflow

Actual behaviour

2019-04-06 23-21-59 的屏幕截图
XXX

Steps to reproduce:

import tensorflow as tf
tf.

Logs

Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

XXX

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

XXX
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Apr 6, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Apr 8, 2019
@ericsnowcurrently
Copy link

Thanks for letting us know about this problem, @benbenji. This is a known upstream issue. See #3515 (which you opened). I'm going to check with upstream.

Just to verify, do you still have the same problem with both the language server and Jedi. Set "python.jediEnabled" to both true and false.

@ericsnowcurrently ericsnowcurrently added area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. info-needed Issue requires more information from poster needs upstream fix bug Issue identified by VS Code Team member as probable bug labels Apr 15, 2019
@jakebailey
Copy link
Member

Can you please test this using the beta channel of the language server?

"python.analysis.downloadChannel": "beta"

@DonJayamanne
Copy link

Its been a month since the information was requested. Closing due to inactivity.
We'll be happy to reopen the issue once the requested information has been provided.

@ghost ghost removed info-needed Issue requires more information from poster needs upstream fix labels May 20, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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
Development

No branches or pull requests

4 participants