Pycharm ошибка при импорте

I’m having trouble with using ‘requests’ module on my Mac. I use python34 and I installed ‘requests’ module via pip. I can verify this via running installation again and it’ll show me that module is already installed.

15:49:29|mymac [~]:pip install requests
Requirement already satisfied (use --upgrade to upgrade): requests in /opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages

Although I can import ‘requests’ module via interactive Python interpreter, trying to execute ‘import requests’ in PyCharm yields error ‘No module named requests’. I checked my PyCharm Python interpreter settings and (I believe) it’s set to same python34 as used in my environment. However, I can’t see ‘requests’ module listed in PyCharm either.

It’s obvious that I’m missing something here. Can you guys advise where should I look or what should I fix in order to get this module working? I was living under impression that when I install module via pip in my environment, PyCharm will detect these changes. However, it seems something is broken on my side …

answered Jul 19, 2019 at 6:52

The solution is easy (PyCharm 2021.2.3 Community Edition).
I’m on Windows but the user interface should be the same.
In the project tree, open External libraries > Python interpreter > venv > pyvenv.cfg.
Then change:

include-system-site-packages = false

to:

include-system-site-packages = true

answered Nov 18, 2021 at 16:42

Before going further, I want to point out how to configure a Python interpreter in PyCharm:
[SO]: How to install Python using the «embeddable zip file» (@CristiFati’s answer). Although the question is for Win, and has some particularities, configuring PyCharm is generic enough and should apply to any situation (with minor changes).

There are multiple possible reasons for this behavior.

1. Python instance mismatch

• Happens when there are multiple Python instances (installed, VEnvs, Conda, custom built, …) on a machine. Users think they’re using one particular instance (with a set of properties (installed packages)), but in fact they are using another (with different properties), hence the confusion. It’s harder to figure out things when the 2 instances have the same version (and somehow similar locations)

• Happens mostly due to environmental configuration (whichever path comes 1^st in ${PATH}, aliases (on Nix), …)

• It’s not PyCharm specific (meaning that it’s more generic, also happens outside it), but a typical PyCharm related example is different console interpreter and project interpreter, leading to confusion

• The fix is to specify full paths (and pay attention to them) when using tools like Python, PIP, …. Check [SO]: How to install a package for a specific Python version on Windows 10? (@CristiFati’s answer) for more details

• This is precisely the reason why this question exists. There are 2 Python versions involved:

  1. Project interpreter: /Library/Frameworks/Python.framework/Versions/3.4

  2. Interpreter having the Requests module: /opt/local/Library/Frameworks/Python.framework/Versions/3.4

  well, assuming the 2 paths are not somehow related (SymLinked), but in latest OSX versions that I had the chance to check (Catalina, Big Sur, Monterey) this doesn’t happen (by default)

When dealing with this kind of error, it always helps (most likely) displaying the following information (in a script or interpreter console):

import os
import sys


print("Executable:", sys.executable)
print("Version:", sys.version)
print("CWD:", os.getcwd())
print("UName:", getattr(os, "uname", lambda: None)())
for evn in ("PATH", "PYTHONHOME", "PYTHONPATH"):
    print("{:s}: {:}".format(evn, os.environ.get(evn)))
print("sys.path:", sys.path)

2. Python‘s module search mechanism misunderstanding

• According to [Python.Docs]: Modules — The Module Search Path:

  When a module named spam is imported, the interpreter first searches for a built-in module with that name. These module names are listed in sys.builtin_module_names. If not found, it then searches for a file named spam.py in a list of directories given by the variable sys.path. sys.path is initialized from these locations:

  • The directory containing the input script (or the current directory when no file is specified).

  • PYTHONPATH (a list of directory names, with the same syntax as the shell variable PATH).

  • The installation-dependent default (by convention including a site-packages directory, handled by the site module).

  A module might be located in the current dir, or its path might be added to ${PYTHONPATH}. That could trick users into making them believe that the module is actually installed in the current Python instance (‘s site-packages). But, when running the current Python instance from a different dir (or with different ${PYTHONPATH}) the module would be missing, yielding lots of headaches

• A somewhat related scenario: [SO]: ModuleNotFoundError: No module named ‘cryptography.hazmat’; ‘cryptography’ is not a package (@CristiFati’s answer)

• For a fix, check [SO]: How PyCharm imports differently than system command prompt (Windows) (@CristiFati’s answer)

3. A PyCharm bug

• Not very likely, but it could happen. An example (not related to this question): [SO]: PyCharm 2019.2 not showing Traceback on Exception (@CristiFati’s answer)

• To fix, follow one of the options from the above URL

4. A glitch

• Not likely, but mentioning anyway. Due to some cause (e.g.: HW / SW failure), the system ended up in an inconsistent state, yielding all kinds of strange behaviors

• Possible fixes:

  • Restart PyCharm

  • Restart the machine

  • Recreate the project (remove the .idea dir from the project)

  • Reset PyCharm settings: from menu select File -> Manage IDE Settings -> Restore Default Settings…. Check [JetBrains]: Configuring PyCharm settings or [JetBrains.IntelliJ-Support]: Changing IDE default directories used for config, plugins, and caches storage for more details

  • Reinstall PyCharm

  Needless to say that the last 2 options should only be attempted as a last resort, and only by experts, as they might mess up other projects and not even fix the problem

Not directly related to the question, but posting:

• [SO]: Run / Debug a Django application’s UnitTests from the mouse right click context menu in PyCharm Community Edition? (a PyCharm related investigation from a while ago)

• [SO]: ImportError: No module named win32com.client (@CristiFati’s answer)

answered Aug 15, 2022 at 16:07

If any one faces the same problem that he/she installs the python packages but the PyCharm IDE doesn’t shows these packages then following the following steps:

1. Go to the project in the left side of the PyCharm IDE then
2. Click on the venv library then
3. Open the pyvenv.cfg file in any editor then
4. Change this piece of code (include-system-site-packages = flase) from false to true
5. Then save it and close it and also close then pycharm then
6. Open PyCharm again and your problem is solved.
   Thanks

answered Jul 24, 2022 at 8:47

answered Jun 24, 2020 at 11:33

For Anaconda:

Start Anaconda Navigator -> Enviroments -> «Your_Enviroment» -> Update Index -> Restart IDE.

Solved it for me.

answered Aug 6, 2021 at 21:23

After pip installing everything I needed. I went to the interpreter and re-pointed it back to where it was at already.
My case: python3.6 in /anaconda3/bin/python using virtualenv…

Additionally, before I hit the plus «+» sign to install a new package. I had to deselect the conda icon to the right of it. Seems like it would be the opposite, but only then did it recognize the packages I had/needed via query.

answered Feb 1, 2019 at 19:42

In my case the packages were installed via setup.py + easy_install, and the they ends up in *.egg directories in site_package dir, which can be recognized by python but not pycharm.

I removed them all then reinstalled with pip install and it works after that, luckily the project I was working on came up with a requirements.txt file, so the command for it was:

pip install -r ./requirement.txt

answered Jul 8, 2019 at 10:32

I just ran into this issue in a brand new install/project, but I’m using the Python plugin for IntelliJ IDEA. It’s essentially the same as PyCharm but the project settings are a little different. For me, the project was pointing to the right Python virtual environment but not even built-in modules were being recognized.

It turns out the SDK classpath was empty. I added paths for venv/lib/python3.8 and venv/lib/python3.8/site-packages and the issue was resolved. File->Project Structure and under Platform Settings, click SDKs, select your Python SDK, and make sure the class paths are there.

answered May 22, 2020 at 16:58

pip install --user discord

above command solves my problem, just use the «—user» flag

answered Feb 26, 2022 at 17:08

I fixed my particular issue by installing directly to the interpreter. Go to settings and hit the «+» below the in-use interpreter then search for the package and install. I believe I’m having the issue in the first place because I didn’t set up with my interpreter correctly with my venv (not exactly sure, but this fixed it).

I was having issues with djangorestframework-simplejwt because it was the first package I hadn’t installed to this interpreter from previous projects before starting the current one, but should work for any other package that isn’t showing as imported. To reiterate though I think this is a workaround that doesn’t solve the setup issue causing this.

answered Jul 6, 2022 at 7:15

—WINDOWS—
if using Pycharm GUI package installer works fine for installing packages for your virtual environment but you cannot do the same in the terminal,

this is because you did not setup virtual env in your terminal, instead, your terminal uses Power Shell which doesn’t use your virtual env

there should be (venv) before you’re command line as shown instead of (PS)

if you have (PS), this means your terminal is using Power Shell instead of cmd

to fix this, click on the down arrow and select the command prompt

select command prompt

now you will get (venv) and just type pip install #package name# and the package will be added to your virtual environment

answered Sep 17, 2022 at 20:54

I tried all the answers but non of them worked!

«»IF YOU ARE LAZY!! Temporary Answer is : «»

you should consider finding the path PyCharm is really installing libraries via pip in terminal and add that to your project like in the next pictures!

1_ go to interpreter settings :

2_ click on «Show All» :

3_ find your current projects interpreter and click on show Paths for selected interpreter :

4_ Now try adding different paths that you think might pip be installing libraries to and it adds all the libraries from that path to your new project :

answered Jun 23 at 19:44

On windows I had to cd into the venv folder and then cd into the scripts folder, then pip install module started to work

cd venv
cd scripts
pip install module

answered Nov 24, 2019 at 9:36

instead of running pip install in the terminal -> local use terminal -> command prompt

see below image

pycharm_command_prompt_image

answered Nov 17, 2020 at 17:42