6

I have 1 file, i get as far as line 1 import requests, nothing more yet and I receive the following error ModuleNotFoundError: No module named 'requests'.

  1. Using Visual Studio Code, installed today with standalone Python x64 3.7.4
  2. Python Extension installed in VSCODE
  3. venv created within VSCODE as a subfolder of workspace withint VSCODE terminal and was recognized by VSCODE when created and I am using venv interpreter in VSCODE as indicated on bottom bar
  4. ran pip install requests within terminal inside VSCODE - completed successfully
  5. ran pip freeze to confirm requests==2.22.0 is registered
  6. Verified pylint was installed in venv

I cannot figure out why VSCODE python interpreter will not recognize that requests is installed

Gama11
  • 31,714
  • 9
  • 78
  • 100
Brandon Meyer
  • 98
  • 1
  • 1
  • 7

6 Answers6

8

try get python version in vscode terminal 

python --version

and check python version vscode IDE used by clicking left buttom corner. enter image description here

make sure these 2 versions are consistent. if not, select the version of IDE with the same version of your terminal.

Will Wu
  • 553
  • 4
  • 15
5

Have you checked your user and workspace settings?

Make sure your workspace settings (not your user settings) points to your project's venv path.

I have encountered a similar problem such as yours but was able to solve it by changing the workspace settings python path to point to my venv path as below.

{
    "python.pythonPath": "${workspaceFolder}/code/venv/bin/python"
}
Nico_Robin
  • 89
  • 1
  • 9
  • This solved a similar problem for me when the AREPL extension was having this problem, but running the program normally worked. Trying this in the AREPL Python path allowed AREPL to find the module. – Kevin Peter Oct 09 '20 at 03:32
1

Is there more than one python environment locally? maybe try:

pip3.7 install requests
oaixnah
  • 44
  • 2
1

Thanks for the responses. I found out my own issue after a few hours.

First off I figured out somewhere that when I was running the terminal in VSCODE it was running against global interpreter. I then tried ./pip freeze and it worked as expected. This told me that the terminal was connected to the wrong interpreter.

For some reason when I would 'run' the file it was executing in the terminal but it wasn't 'activating' the venv. I've closed and reopened VSCODE many times but for some reason when I closed the terminal window and reopened using CTRL+SHIFT+' and I received an error about signed scripts when it tried to activate my venv using the PS1 script. I ran Set-ExecutionPolicy -ExecutionPolicy RemoteSigned inside a normal PowerShell window and then reopened the Terminal window in VSCODE and it successfully activated my venv and I know see my venv name at the beginning of the line of the terminal. I then ran 'pip freeze' to confirm which modules installed inside of venv and then ran again in normal powershell window and it was different.

There is documentation somewhere that says to run Set-ExecutionPolicy -ExecutionPolicy RemoteSigned which I found later, but it would have been nice to know this was a requirement.

Brandon Meyer
  • 98
  • 1
  • 1
  • 7
  • 2
    Best practice is to always run pip via `python -m pip` to guarantee it is being run against the interpreter that you expect. Helps to avoid when `pip` is bound to a Python installation/interpreter that you weren't expecting. – Brett Cannon Sep 30 '19 at 23:42
1

2 ways work for me, under windows 10:

  1. Run in terminal: CTRL + F5
  2. Add the following in settings json:
"code-runner.executorMap": {
  "python": "$pythonPath -u $fullFileName"
}
Tyler2P
  • 2,324
  • 26
  • 22
  • 31
Fen
  • 81
  • 1
  • 1
0

Try using:

pip3 install requests
Tyler2P
  • 2,324
  • 26
  • 22
  • 31
radhadman
  • 115
  • 8