How to Install Python Packages from requirements.txt Using pip and a Local Directory

By the end of this page, you will understand how pip install -r requirements.txt works with local package sources, what the -f option actually does, why package metadata output does not always mean installation succeeded, and how to correctly install and verify packages inside a Python virtual environment.

pip can install packages listed in a requirements.txt file, and it can also look in extra places for package files such as wheels or source archives. A common misunderstanding is thinking that -f means “install everything from this folder.” It does not.

The -f flag means find links. It tells pip to search a directory or page for candidate package files that match the requirements. pip still resolves each requirement individually and only installs packages if it finds valid distributions and successfully completes the installation.

In older versions of pip, the output could be misleading. Messages like:

Running setup.py egg_info for package ...

mean that pip is reading package metadata, not that the package has been fully installed.

For installation to actually succeed:

• the virtual environment must be activated correctly
• pip must be the one inside that virtual environment
• the local directory must contain installable package files
• the package versions in requirements.txt must match available files
• the install command must complete successfully, including dependencies if needed

This matters in real programming because many teams install dependencies from:

Think of requirements.txt as a shopping list and the local archive directory as a warehouse.

• requirements.txt says what you need.
• -f file:///path/to/archive/ tells pip where to look for items.
• pip checks the warehouse shelves for matching packages.
• Reading egg_info is like checking the label on a box.
• Actual installation is like taking the item home and placing it in your cupboard.

So if pip only checks labels but never finishes the install, the package will not end up in site-packages.

The key idea: finding a package is not the same as installing it.

The usual syntax is:

pip install -r requirements.txt

To tell pip to also search a local directory for packages:

pip install -r requirements.txt -f file:///absolute/path/to/archive/

If you want to avoid downloading from the internet and only use local files, a more explicit modern approach is:

pip install --no-index --find-links=file:///absolute/path/to/archive/ -r requirements.txt

Example

Suppose your local folder contains:

• Django-1.3.tar.gz
• Jinja2-2.5.5.tar.gz
• South-0.7.3.tar.gz

And your requirements.txt contains:

Django==1.3
Jinja2==2.5.5
South==0.7.3

Then install with:

source testing/bin/activate
python -m pip install --no-index --find-links=file:///absolute/path/to/archive/ -r requirements.txt

Why use python -m pip?

Consider this command:

python -m pip install --no-index --find-links=file:///packages/ -r requirements.txt

And this requirements.txt:

Jinja2==2.5.5

Step-by-step

1. python -m pip runs pip using the current Python interpreter.
2. -r requirements.txt tells pip to read package names and versions from the file.
3. --no-index tells pip not to contact PyPI.
4. --find-links=file:///packages/ tells pip to search that local directory for matching package files.
5. pip scans the directory for a package matching Jinja2==2.5.5.
6. If it finds a valid distribution file, it reads metadata first.
7. If installation succeeds, files are copied into the virtual environment's site-packages.
8. If installation fails, the package will not be importable.

Trace example

Installing from a local directory is common in situations like these:

• Offline servers: production machines may not have internet access.
• Corporate environments: only approved internal packages may be allowed.
• CI/CD pipelines: build systems may use a cached package directory for speed.
• Reproducible deployments: teams may freeze exact package files and install only from those files.
• Air-gapped systems: security-sensitive environments often rely on local package mirrors.

Example scenarios

• A deployment script installs all dependencies from a shared network folder.
• A Docker image copies prebuilt wheels into /wheels and installs from there.
• A test runner uses a local cache to avoid repeated downloads.

In all of these, developers usually combine requirements.txt with either --find-links or a proper package index mirror.

In real projects, developers usually make local installs more reliable with a few patterns.

1. Use python -m pip

Instead of:

pip install -r requirements.txt

prefer:

python -m pip install -r requirements.txt

This avoids using the wrong pip binary.

2. Use explicit offline mode

If the install must come only from local files:

python -m pip install --no-index --find-links=file:///wheels/ -r requirements.txt

3. Verify after installation

Teams often run checks such as:

python -m pip list
python -m pip check

4. Use guard checks in scripts

Deployment scripts may include early validation:

python -m pip --version
python -c "import sys; print(sys.executable)"

This confirms the active interpreter and environment.

5. Prefer wheel files when possible

Wheels install faster and more reliably than source archives because they do not need a build step.

6. Keep requirements and package files aligned

Here are the most common beginner mistakes when installing from a local directory.

1. Assuming -f means “install everything in this folder”

It does not. It only adds an extra location where pip looks for packages.

Broken assumption:

pip install -r requirements.txt -f file:///packages/

This only works if the folder contains valid files matching the requested requirements.

2. Using the wrong pip

You may activate a virtual environment but still run a different pip from somewhere else.

Check with:

which python
which pip
python -m pip --version

Safer command:

python -m pip install -r requirements.txt

3. Thinking egg_info means installation completed

Output like this:

Running setup.py egg_info for package Fabric

only means package metadata is being read.

4. Local directory does not contain installable files

# Activate virtual environment
source testing/bin/activate

# Safest way to run pip in the active environment
python -m pip --version

# Install from requirements file
python -m pip install -r requirements.txt

# Install using a local package directory
python -m pip install --find-links=file:///absolute/path/to/archive/ -r requirements.txt

# Install only from local files, not PyPI
python -m pip install --no-index --find-links=file:///absolute/path/to/archive/ -r requirements.txt

# Verify installed packages
python -m pip list
python -m pip show Django
python -c "import django; print(django.get_version())"

# Check interpreter location
python -c "import sys; print(sys.executable)"

Key rules

• -r reads requirements from a file.
• -f / --find-links adds a search location for package files.
• --no-index prevents internet lookup.
• egg_info output is not proof of successful installation.
• Prefer python -m pip over plain pip.
• Use absolute file:///... paths for local directories.
• Ensure versions in requirements.txt match files in the archive.

Why did pip show package activity but nothing appeared in site-packages?

Because pip may have only read package metadata such as egg_info, or the install may have failed before completion.

Does -f mean install all packages from a directory?

No. It only tells pip where to look for files that satisfy the requirements you requested.

How do I force pip to use only local files?

Use:

python -m pip install --no-index --find-links=file:///absolute/path/to/archive/ -r requirements.txt

How can I check whether I installed into the correct virtual environment?

Run:

python -m pip --version
python -c "import sys; print(sys.executable)"

These should point to your virtual environment.

What kinds of files should be in the local archive directory?

Usually installable package distributions such as .whl, .tar.gz, or .zip files.

• virtualenv — Creates isolated Python environments so dependencies do not mix.
• requirements.txt — Lists the packages and versions a project depends on.
• pip install — Core command for installing Python packages.
• wheel — A built package format that installs faster and more reliably than source archives.
• site-packages — The directory where installed Python packages live.
• Python import system — Helps explain why installed packages can or cannot be imported.
• dependency management — Covers how projects control versions and installation sources.
• package indexes and mirrors — Related because local installs often use internal or offline package sources.