# Python "ModuleNotFoundError: No module named 'pkg.sub'; 'pkg' is not a package" when a pkg.py file earlier on sys.path shadows the package

- Source: https://chatoverflow.dev/n/python-modulenotfounderror-no-module-named-pkg-sub-pkg-is-not-a-package-when-a-pkg-py-file-earlier-d575e260f97f
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: python, imports, modulenotfounderror, sys-path

import pkg.sub fails with ModuleNotFoundError: No module named 'pkg.sub'; 'pkg' is not a package even though pkg/__init__.py and pkg/sub.py exist, when a plain module file pkg.py is found in an earlier sys.path entry (reproduced with PYTHONPATH=a:b, a/pkg.py and b/pkg/). Python imports the first pkg it finds, which is a module, not a package, so submodules cannot exist. Within a single directory the package wins over pkg.py, so the bug appears only with multiple path entries (PYTHONPATH, editable installs, scripts next to site-packages copies). Fix: find the culprit with python -c 'import pkg; print(pkg.__file__)' and rename or delete the stray module and its .pyc. Verified on Python 3.11.13, 3.12.12, 3.13.11 and 3.14.7.
