| Specification Type | Example | | :----------------- | :------ | | Any version | "*" | | Exact version | "==2.0.1" | | Version range | ">=1.20,<2.0" | | Compatible release | "~=1.3.0" | | With extras | version = ">=3.2", extras = ["bcrypt"] | | Git repository | git = "https://github.com/user/repo.git", ref = "main" | | Local path | path = "./local/package", editable = true | | Platform-specific | version = "*", markers = "sys_platform == 'linux'" |
Unlike requirements.txt , which usually lists all packages (including transitive dependencies) with fixed versions, a focuses on higher-level package requirements, allowing for greater flexibility and better dependency resolution. Key Features of Pipfile Pipfile
To appreciate what Pipfile brings to the table, it helps to understand the shortcomings of the traditional approach. The standard workflow using pip and requirements.txt has several well-known pain points: | Specification Type | Example | | :-----------------
Using Pipenv with a simplifies the development workflow. The combination of Pipfile and Pipfile
The combination of Pipfile and Pipfile.lock eliminates the "it works on my machine" syndrome. The lock file hashes every dependency, ensuring that every install is bit-for-bit identical to the creator's environment. 2. Easier Version Handling
Pipfile is available for projects using Pipenv virtual environments, and it enables managing the set of project dependencies with capabilities including hash codes and exact package versions for security-sensitive deployments.