To resolve the issue, perform the following steps:

1. Open the Command Palette by pressing Ctrl+Shift+P on your keyboard.
2. In the Command Palette, select Python: Clear Cache and Reload Window.

Two methods below:

1. In VS code you can edit the setting.json file. If you add "python.analysis.useImportHeuristic": true the linting error will be removed.

2. The alternative is to add # type: ignore at the end of the import code.

Here is the github link that i got the above resolution from: https://github.com/microsoft/pylance-release/issues/68

It worked for me: python 3.9, VScode, windows10

I faced the same error some days ago. This is how I fixed it.

1. Copy the path to your Python interpreter in your virtual environment folder.
2. Press Ctrl + Shift + P to open command pallete. Choose the Python: Select Interpreter
3. Choose Enter Interpreter Path
4. Paste the path you copied. So it should look like ./<Project_Folder>/env/bin/python. Click Enter

And it's solved.

Also, on some occasions, you might have configured your environment by adding custom paths that Pylance can not detect.

In that case, you can use the python.analysis.extraPaths parameter to add more paths to your project, such as :

"python.analysis.extraPaths": ["app", "another/path/etc"]

(Source: https://dev.to/climentea/how-to-solve-pylance-missing-imports-in-vscode-359b)

I had a similar problem in my setup as I create a virtual environment per project and install Jupyter there. Instead of a global setting change in the Pylance extension, I rather prefer to follow what states its troubleshooting guide.

Suppose your virtual environment is called venv and it is inside your project folder:

• Create a folder called .vscode at the root of your project folder, if it does not already exist. Don't forget the dot in front of the name.
• Create or edit the file .vscode/settings.json and include this tag:

{
    "python.analysis.extraPaths": ["./venv"]
}

• Note that the path to your virtual environment is relative to the root project folder, not the folder containing the settings.json file.

I hope this helps.

tldr;

TensorFlow defines some of its modules in a way that pylint & pylance aren't able to recognize. These errors don't necessarily indicate an incorrect setup.

To Fix:

• pylint: The pylint warnings are safely ignored.
• Intellisense: The best way I know of at the moment to fix Intellisense is to replace the imports with the modules they are aliasing (found by importing alias in a repl as x then running help(x)). Because the target of the alias in my case is an internal name, you probably don't want to check in these changes to source control. Not ideal.

Details

Regarding the linting: It seems that tensorflow defines its modules in a way that the tools can't understand. Also, it appears that the package is an alias of some kind to another package. For example:

import tensorflow.compat.v1 as tf
tf.estimator.RunConfig()

The above code gives the pylint warning and breaks intellisense. But if you manually import the above in a REPL and run help(tf), it shows you the below package, which you can use instead:

import tensorflow_core._api.v1.compat.v1 as tf
tf.estimator.RunConfig()

This second example does not cause the pylint warning. Also the Intellisense features (Go to definition, Ctrl+Click, etc) work with this second example.

However, based on the _api, it looks like that second package name is an internal namespace, so I'm guessing it is probably best to only use this internal name for local debugging.

Confirmation/Tickets

• pylint: I've found a ticket about pylint having issues with a couple tensorflow imports that looks related.
• Intellisense: I've opened a ticket with pylance.