Summary

Adds a new --no-lock flag to the pipenv requirements command that generates requirements using version specifiers from the Pipfile instead of locked versions from Pipfile.lock.

Motivation

This addresses issue #5482 where users requested the ability to generate requirements.txt with flexible version constraints suitable for Python libraries.

Python libraries typically need looser version constraints (like >=1.0, *) in their install_requires rather than strictly pinned versions (like ==1.2.3) that come from the lockfile. Strictly pinned dependencies can cause conflicts when the library is installed alongside other packages.

Usage

# Generate requirements with Pipfile version specifiers
pipenv requirements --no-lock

# Include dev dependencies
pipenv requirements --no-lock --dev

# Specific categories
pipenv requirements --no-lock --categories="packages,extras"

Examples

Given a Pipfile:

[packages]
requests = ">=2.0"
flask = "*"
django = "~=4.0"

With --no-lock:

requests>=2.0
flask
django~=4.0

Without --no-lock (current behavior):

requests==2.32.3
flask==3.0.0
django==4.2.7

Implementation Details

• The --no-lock flag implies --from-pipfile since only direct dependencies make sense without the lockfile
• Supports all Pipfile dependency types: simple versions, VCS, paths, editable installs
• Preserves extras (e.g., package[extra1,extra2])
• Preserves markers (e.g., sys_platform == 'win32')
• Hashes are not supported with --no-lock (they require locked versions)

Files Changed

• pipenv/cli/command.py - Added --no-lock option
• pipenv/routines/requirements.py - Added Pipfile-based generation logic
• pipenv/utils/requirements.py - Added requirements_from_pipfile() function

Fixes #5482

Pull Request opened by Augment Code with guidance from the PR author