Error AtlasError Documentation and Resolutionpip documented errors
Browse documented pip errors with exact messages, troubleshooting context, and practical remediation steps.
Configuration
Configuration errors
Could not open requirements filepip could not open the requirements filepip could not read the requirements file passed with -r because the file path was wrong, missing, or not available from the current working directory.
Invalid requirementpip could not parse the requirement specifierpip rejected one of the requirement lines because the package specifier, URL, marker, or requirements-file syntax is invalid.
Networking
Networking errors
There was a problem confirming the ssl certificatepip could not confirm the SSL certificate for the package index connectionpip could not establish a trusted HTTPS connection to the package index because certificate validation failed or the configured trust chain is incomplete.
CERTIFICATE_VERIFY_FAILEDpip failed TLS certificate verificationpip could not verify the HTTPS certificate presented during package download, often because of proxy certificates, custom trust roots, or outdated certificate handling.
Package Managers
Package Managers errors
No matching distribution foundpip cannot find a compatible package versionpip cannot install the requested package because the package name, version, or Python interpreter compatibility does not match any available release.
ResolutionImpossiblepip cannot resolve conflicting dependency requirementspip could not find a dependency set that satisfies all of the requested packages and their version constraints.
requires <package>, which is not installedpip check found a missing required packagepip check found that an installed package depends on another package that is missing from the environment.
requires WebOb, which is not installedpip check found a required package that is not installedpip check found an installed package with a declared dependency that is missing from the current environment.
has requirement X, but you have Ypip check found an installed dependency with the wrong versionpip check found an installed dependency version that does not satisfy the requirement declared by another installed package.
has requirement <package><version>, but you have <package> <version>pip check found an installed dependency with the wrong versionpip check found that an installed package depends on a version range that the currently installed dependency does not satisfy.
No broken requirements foundpip check reported that no broken requirements were foundpip check completed successfully and found that installed packages have compatible dependency requirements in the current environment.
Directory is not installablepip could not install a local directory because it is not a Python projectpip was asked to install a local directory, but the folder does not contain the project metadata files pip needs to treat it as an installable Python package.
ResolutionTooDeepErrorpip dependency resolution went too deeppip's dependency resolver exceeded its search depth while trying to find a compatible set of package versions, usually because the dependency graph is large or highly constrained.
Requires-Pythonpip found a package that does not support the current Python versionpip skipped candidate releases because their `Requires-Python` metadata does not match the interpreter version being used for installation.
THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILEpip found package hashes that do not match the requirements filepip refused to install because the downloaded distribution hash does not match the hash pinned in the requirements file.
externally-managed-environmentpip refused to modify an externally managed Python environmentpip refused to install into the current Python environment because the environment is externally managed by the operating system or distributor tooling.
Security
Security errors
--require-hashespip require-hashes mode failed because dependencies were missing hashespip refused to continue in hash-checking mode because not every dependency was explicitly listed and hashed, which would weaken repeatable install guarantees.
--require-hashespip require-hashes mode failed because requirements were not fully pinnedpip entered hash-checking mode but found a requirement that was not pinned to an exact version, which makes repeatable secure installs impossible.