python module not found error but folder exists

stackoverflow.com › questions › 58084072 › python-module-not-found-but-exists-in-folder

Python module not found but exists in folder - Stack Overflow

python - ModuleNotFoundError when it actually is in the path

1 of 2

This is a very typical issue, so I will leave this here for future reference.

If I have a project called: my_project

.
└── my_project
    ├── first_folder
    ├── second_folder
    └── third_folder

What you want to do is one of these two things:

PYTHONPATH (only Python)

cd ~/my_project && export PYTHONPATH=$(pwd)

change dir to root dir, and export that dir to PYTHONPATH, so when Python runs it looks in the PYTHONPATH.

PATH (everything)

cd ~/my_project && export PATH=$PATH:$(pwd)

Same as above!

This needed to live somewhere since it took me a while to figure out. So for anyone in the future who needs help with this!

2 of 2

-1

Check the python version you are calling. Run "python --version". If it's not 3.7.1, that's the problem. If it returns a version beginning with "2", then try running the python3 binary instead.

python - ImportError - Module Not Found?

python - ModuleNotFoundError even if the folder in in the system path

Path exists in sys.path but still gives module not found error in Python

python - ModuleNotFoundError even though module/file clearly exists

More results from stackoverflow.com

Improve ModuleNotFoundError to cater for condition when directory exists - Python Help - Discussions on Python.org

Hi, John, welcome to the forum. Unfortunately, I can’t see anything here that could possibly make an actionable suggestion - since it’s based on serious, fundamental misunderstandings of how the existing system actually works. I’m moving this to the Python Help section, and giving a more detailed ex…

1 of 3

2 of 3

Hello! [image] John D. Pope: the directory exists eg. library but python complains - ModuleNotFoundError: No module named library the library directory has the necessary init.py file - but because the code was not invoked with python -m module How was the code invoked? Python can do both p…

Discussions

Python doesn't find local module although it is installed and its location exists in sys.path

I installed a local module using the pyproject.toml approach by following the great tutorial by RealPython: Packaging Your Python Code With pyproject.toml | Complete Code Conversation - YouTube Although the module seems to be locally installed, I am unable to invoke it from outside the project ... More on discuss.python.org

discuss.python.org

March 23, 2023

Module not found but it's already installed

I’m fairly new to Python. I use Python 3.11.8 (what MS Azure supports, my eventual production environment) on Windows 10. I’m testing a program on Windows 10. I have created and activated my virtual environment in the cmd.exe window. My program is in c:\users\MYUSER\onedrive - ... More on discuss.python.org

discuss.python.org

March 26, 2024

ModuleNotFoundError: No module named 'Directory_one'

Hi All, I am trying to access method from another module in one of my file but I keep getting ModuleNotFoundError. This how my folder structure is: Appreciate for your help Thanks Lax More on discuss.python.org

discuss.python.org

August 26, 2021

python - Module not found - "No module named" - Stack Overflow

Here's my Python folder structure -project ----src ------model --------order.py ------hello-world.py Under src, I have a folder named model, which has a Python file called order.py, whose contents More on stackoverflow.com

stackoverflow.com

freeCodeCamp

freecodecamp.org › news › module-not-found-error-in-python-solved

ModuleNotFoundError: no module named Python Error [Fixed]

September 12, 2022 - In Python, you can import modules from other files using absolute or relative paths. For this example, I'll focus on absolute paths. When you try to access a module from the wrong path, you will also get the module not found here. Here's an example: Let's say you have a project folder called test.

Python doesn't find local module although it is installed and its location exists in sys.path - Python Help - Discussions on Python.org

March 23, 2023 - I installed a local module using the pyproject.toml approach by following the great tutorial by RealPython: Packaging Your Python Code With pyproject.toml | Complete Code Conversation - YouTube Although the module seems to be locally installed, I am unable to invoke it from outside the project directory.

Containersolutions

containersolutions.github.io › runbooks › posts › python › module-not-found

Module Not Found – Runbooks

If you are using a pre-3.3 version of Python, then it is a requirement that a Python module contains a file called __init__.py. The inclusion of the file is often forgotten about when creating modules on-the-fly, so is a frequent cause of failure. You may also want to consider whether the user you are running as has the right permissions to access the files and folders (see step 4).

GeeksforGeeks

geeksforgeeks.org › how-to-fix-the-module-not-found-error

How to Fix The Module Not Found Error? - GeeksforGeeks

April 28, 2025 - This error occurs when you have not installed that module on your system and try to access the module that the Python interpreter cannot locate in its search path or in the Python path, If python cannot find the module you're trying to import ...

Towards Data Science

towardsdatascience.com › home › programming › how to fix modulenotfounderror and importerror

How to Fix ModuleNotFoundError and ImportError | Towards Data Science

September 13, 2020 - In most of the cases, either of the errors occur due to the fact that Python is unable to resolve the module's name in sys.path . Recall that when you call import a if the module's name was found neither in sys.modules nor in standard library, ...

GeeksforGeeks

geeksforgeeks.org › python › how-to-fix-the-module-not-found-error

How to Fix The Module Not Found Error - Python

July 1, 2026 - Explanation: package may be installed globally or in another virtual environment, but not in the currently active one. 1. Check Whether the Module is Installed: You can use a try-except block to verify whether a module exists.

Find elsewhere

Google Bing Mojeek

LabEx

labex.io › tutorials › python-how-to-address-module-not-found-errors-in-python-415764

How to address module not found errors in Python | LabEx

This can happen for a variety of reasons, such as: The module is not installed or is not in the Python path. The module is misspelled or named incorrectly. The module is located in a different directory than your script.

Module not found but it's already installed - Python Help - Discussions on Python.org

March 26, 2024 - I’m fairly new to Python. I use Python 3.11.8 (what MS Azure supports, my eventual production environment) on Windows 10. I’m testing a program on Windows 10. I have created and activated my virtual environment in the cmd.exe window. My program is in c:\users\MYUSER\onedrive - ...

ModuleNotFoundError: No module named 'Directory_one' - Python Help - Discussions on Python.org

August 26, 2021 - Hi All, I am trying to access method from another module in one of my file but I keep getting ModuleNotFoundError. This how my folder structure is: Appreciate for your help Thanks Lax

stackoverflow.com › questions › 37233140 › module-not-found-no-module-named

python - Module not found - "No module named" - Stack Overflow

1 of 16

All modules in Python have to have a certain directory structure. You can find details here.

Create an empty file called __init__.py under the model directory, such that your directory structure would look something like that:

.
└── project
    └── src
        ├── hello-world.py
        └── model
            ├── __init__.py
            └── order.py

Also in your hello-world.py file change the import statement to the following:

from model.order import SellOrder

That should fix it

P.S.: If you are placing your model directory in some other location (not in the same directory branch), you will have to modify the python path using sys.path.

2 of 16

If it's your root module, just add it to PYTHONPATH (PyCharm usually does that):

export PYTHONPATH=$PYTHONPATH:<root module path>

For Docker:

ENV PYTHONPATH="${PYTHONPATH}:<root module path in container>"

stackoverflow.com › questions › 51323116 › python-no-module-found-even-though-it-exists-in-directory

Python: No module found even though it exists in directory - Stack Overflow

1 of 2

Three possibilities come to my mind:

The module just works for certain python versions (e.g. 3.5 but not 3.6).
The path where your module is currently located does not appear in sys.path.
The class you want to use must be specified while importing the module because it is not specified in the __init__.py of the module itself.

As far as I can tell, only the first option might cause your problem.
Nevertheless I would make a quick check with

import sys
sys.path

and in case that the correct path is really missing..

sys.path.append('PathToModule')

2 of 2

You will need to do a relative import (PEP-328), but according to this guide, you can only go up until the level where you launched the script from, which is the tests directory in you case.

So you'll either have to add the model directory to the path, or add the source folder of your project to a .pth file in your site-packages as shown here

stackoverflow.com › questions › 24722212 › python-cant-find-module-in-the-same-folder

Python can't find module in the same folder - Stack Overflow

How to Fix Module Not Found Error in Python - ModuleNotFound Error (FIXED) - YouTube

1 of 15

231

Change your import in test.py to:

from .hello import hello1

2 of 15

126

Your code is fine, I suspect your problem is how you are launching it.

You need to launch python from your '2014_07_13_test' directory.

Open up a command prompt and 'cd' into your '2014_07_13_test' directory.

For instance:

$ cd /path/to/2014_07_13_test
$ python test.py

If you cannot 'cd' into the directory like this you can add it to sys.path

In test.py:

import sys, os
sys.path.append('/path/to/2014_07_13_test')

Or set/edit the PYTHONPATH

And all should be well...

...well there is a slight mistake with your 'shebang' lines (the first line in both your files), there shouldn't be a space between the '#' and the '!'

There is a better shebang you should use.

Also you don't need the shebang line on every file... only the ones you intend to run from your shell as executable files.

YouTube

youtube.com › watch

02:55

In this video, I'll show you how you can fix the ModuleNotFound error in Python. The module not found error (ModuleNotFoundError) in python occurs when a spe...

Published: July 25, 2024

reddit.com › r/learnpython › why do i get a modulenotfounderror?

r/learnpython on Reddit: Why do I get a ModuleNotFoundError?

September 2, 2021 -

Hey Guys,

I get a weird ModuleNotFoundError in one of my projects and i do not really understand why. So here is my Folder Structure:

Project\

| main.py

| packageabc\

| | __init__.py

| | abc.py

| | packagexyz\

| | | xyz.py

In every .py file is an abc/xyz or main class. Now the interesting part. Inside the abc.py I do an import like this:

from packagexyz.xyz import xyz

This works perfectly fine!

Inside the main.py I do an import like this:

from packageabc.abcimport abc

Now I get an ModuleNotFoundError. Error Code looks like this:

from packagexyz.xyz import xyz ModuleNotFoundError: no module named packagexyz.

So the import in the abc.py File that works perfectly when tested inside the file does not work if the abc.py file is imported. So why is that?

You probably have a circular dependency - abc imports xyz and xyz imports abc. Python can't complete either import so it raises an error.

1 of 2

2 of 2

It's because of the way Python looks for modules. There's a list of paths that Python looks through to find modules, which automatically includes things like the place pip installs packages to. It also automatically includes the directory the executing script is in. It does not, however, automatically include the directory an imported module is in. So, if you're executing "abc.py" directly, in finds "packagexyz" just fine, since it knows to look in the "packageabc" folder for modules. If you are executing "main.py" instead, the only place it looks (besides the default and manually configured paths) is "Project", so it can't find packagexyz. There's really three ways you could fix this: Manually configuring paths You can keep the imports as you have them and simply ensure that the "packageabc" folder is always on the search path for modules. You can do so either by configuring the PYTHONPATH environment variable to include it or by appending it to sys.path in your "main.py" before importing abc. Absolute imports You could also change the import in "abc.py" to be relative to "Project" (from packageabc.packagexyz.xyz import xyz). Then your "main.py" would work the way it is. Of course, that in turn means you can no longer directly execute "abc.py" unless you manually configure "Project" to always be on the search path for modules. Relative imports You could also change "abc.py" to use relative imports (from .packagexyz.xyz import xyz, note the extra dot in front). Then your "main.py" would work the way it is, as well. You could also still directly execute "abc.py", but only if you make sure to do it in a way that Python is aware it is part of a larger package (otherwise, relative imports give you an error). Specifically, you'd always need to execute it like this: python -m packageabc.abc Rather than like this: python packageabc/abc.py

reddit.com › r/learnpython › modulenotfounderror, but it's there

r/learnpython on Reddit: ModuleNotFoundError, but it's there

September 13, 2023 -

I'm trying to build a "portable" Python package based on those available from https://github.com/indygreg/python-build-standalone/releases.

I've extracted this into /opt/staging/ansible and pip installed ansible without issue (the main purpose of this package will be to allow staging machines to run ansible-pull).

However, I also need the 'firewall' module installed, but after installing it, Python still fails to import it. I confirmed the module library locations:

root@b-test3 /opt/staging/ansible/bin # ./python3 -m 'site'
sys.path = [
    '/opt/staging/ansible/bin',
    '/opt/staging/ansible/lib/python310.zip',
    '/opt/staging/ansible/lib/python3.10',
    '/opt/staging/ansible/lib/python3.10/lib-dynload',
    '/opt/staging/ansible/lib/python3.10/site-packages',
]
USER_BASE: '/root/.local' (doesn't exist)
USER_SITE: '/root/.local/lib/python3.10/site-packages' (doesn't exist)
ENABLE_USER_SITE: True

I even went as far as to manually target the site-packages directory:

# ./pip3 install -Ut /opt/staging/ansible/lib/python3.10/site-packages/ firewall
Collecting firewall
  Using cached firewall-0.2.0-py3-none-any.whl
Collecting boto (from firewall)
  Using cached boto-2.49.0-py2.py3-none-any.whl (1.4 MB)
Collecting ec2>=0.2 (from firewall)
  Using cached ec2-0.4.0-py2.py3-none-any.whl (6.2 kB)
Installing collected packages: boto, ec2, firewall
Successfully installed boto-2.49.0 ec2-0.4.0 firewall-0.2.0

But still...

root@b-test3 /opt/staging/ansible/bin # ./python3
Python 3.10.13 (main, Aug 26 2023, 07:12:19) [Clang 16.0.3 ] on linux
Type "help", "copyright", "credits" or "license" for more information.
Cannot read termcap database;
using dumb terminal settings.
>>> import firewall
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'firewall'
>>>

I've checked all the usual suspects I can think of. This is an Oracle Linux 8 VM, so it's got Python3.6 by default. I can install firewall there and import it no problem.

In my Python 3.10 package, I can install other modules without issue (and without any tricks). Ansible installed fine and runs as expected. I also installed pandas as a test and could import it successfully.

Anyone got any clues why firewall isn't working?