All 15 Modules & Packaging questions
More in Modules & Packaging
What does the __init__.py file do inside a package directory? How does Python's module import system avoid re-executing a module multiple times when imported from different places? What is the difference between an absolute import and a relative import within a package? What does the `if __name__ == '__main__':` idiom accomplish, and why is it important for modules? How does pyproject.toml serve as the modern standard for defining a Python package's build configuration and dependencies? What is __all__ and how does it control `from module import *` behavior? What is the purpose of a `requirements.txt` file, and how does it differ from dependency declarations in pyproject.toml? What does 'editable install' (pip install -e .) mean, and why is it useful during development? How does Python locate modules during import, and what is sys.path's role? What is a namespace package, and how does it differ from a regular package?
Advertisement
Back to results for “Virtual Environments & Dependency Management”
Python › Modules & Packaging

What is the difference between a module and a package in Python?

Beginner

Answer

A module is a single .py file containing Python definitions and statements that can be imported. A package is a directory containing multiple modules plus an __init__.py file (making it importable as a namespace), allowing related modules to be organized hierarchically, e.g., `import package.module`.
# mymodule.py is a module
import mymodule

# mypackage/ with __init__.py is a package
import mypackage.submodule
Real-world example A web application's codebase organizes routes.py, models.py, and utils.py as modules inside an `app` package, giving a clean `from app.models import User` import path.

Common follow-ups: Do packages require __init__.py in modern Python?;What is a namespace package?

Modules & Packaging;Virtual Environments & Dependency Management
All 15 Modules & Packaging questions