Skip to content

Intellisense not working with TensorFlow 2.0 #5350

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
david-macleod opened this issue Apr 17, 2019 · 2 comments
Closed

Intellisense not working with TensorFlow 2.0 #5350

david-macleod opened this issue Apr 17, 2019 · 2 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

@david-macleod
Copy link

Environment data

  • VS Code version: 1.33.1
  • Extension version (available under the Extensions sidebar): 2019.3.6558
  • OS and version: Windows 10
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6.8 Anaconda
  • Type of virtual environment used: conda
  • Relevant/affected Python packages and their versions:
  • tensorflow==2.0.0-alpha0
  • Microsoft Python Language Server version 0.2.59.0

Expected behaviour

When I hover over a variable I see the object definition (this is example is using tensorflow=1.12.0)

image

Actual behaviour

When using tensorflow==2.0.0-alpha0 I see no object description in the hover overlay
image

Steps to reproduce:

  1. Install tensorflow
  2. Import an object and hover over with cursor

Logs

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

************* Module 
2,0,error,no-name-in-module:No name 'keras' in module 'tensorflow'
2,0,error,import-error:Unable to import 'tensorflow.keras.layers'
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Apr 17, 2019
@DonJayamanne DonJayamanne added area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. needs upstream fix bug Issue identified by VS Code Team member as probable bug labels Apr 18, 2019
@ghost ghost removed triage-needed Needs assignment to the proper sub-team labels Apr 18, 2019
@SimantoR
Copy link

Any updates on this? I was looking for a PR for this maybe

@DonJayamanne
Copy link

This issue is being tracked upstream on the Language Server repo. Please check the following issue for updates microsoft/python-language-server#818

@ghost ghost removed the needs upstream fix label Apr 22, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 20, 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

3 participants