Reference only

No matching distribution found: check Python tags, platform and package identity

pip needs a candidate compatible with the requested package/version, Python, operating system, architecture and configured index. No candidate does not necessarily mean that the project does not exist.

Symptoms and scope

pip needs a candidate compatible with the requested package/version, Python, operating system, architecture and configured index. No candidate does not necessarily mean that the project does not exist.

Error fragments for search; IDs, values and filenames may vary:

No matching distribution found
Could not find a version that satisfies the requirement

Source-supported context

pip's installation and debugging facilities expose candidate selection and supported wheel tags. Source distributions and prebuilt wheels have different prerequisites. Source 1 Source 2 Source 3 Source 4

Cases to distinguish

1. No wheel matches this Python or platform, and the requested version has no supported alternative.

2. An index, mirror or TLS failure prevents pip from seeing available candidates.

3. The wrong distribution name, release version or renamed wheel was supplied.

Diagnostic sequence

The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.

Step 1. Confirm the exact requirement against the node author's source, including version constraints and the install name.

Step 2. Record Python and pip versions and inspect supported tags with pip debug --verbose. Do not infer compatibility from the wheel's friendly filename alone.

Step 3. Verify the configured index and earlier network errors. Compare with the publisher's official distribution information.

Step 4. Use a separately created supported environment, or the author's supported source-build path when prerequisites are available. Keep the working installation intact.

Commands and request examples

Use the environment and shell identified above. Paths and variables are examples to adapt; these commands/snippets were not executed for your machine.

python --version
python -m pip --version
python -m pip debug --verbose

Completion check

The selected artifact is compatible with the actual runtime, installs successfully and passes its import/operation check.

Limitations and cautions

Do not downgrade system Python in place or install random third-party wheels simply to suppress this message.

Original sources

Localization prepared: 2026-09-22. The source-check dates above were inherited from the existing article; this translation does not claim they were all rechecked today. No GPU run, minimum-memory measurement or runtime guarantee is supplied.

Didn't solve it?

Check the next possible cause

The same symptom can come from a different cause. Work through these related entries in order.

  1. pip certificate verification failed: repair trust without disabling TLSCERTIFICATE_VERIFY_FAILEDDiagnose the failing hostname, certificate chain and interpreter before treating HTTPS verification as an inconvenience to bypass.
  2. ModuleNotFoundError in ComfyUI even though the package is installedModuleNotFoundErrorA successful installation in a terminal does not show that ComfyUI uses the same Python. Separate the import name, distribution name and running interpreter before changing dependencies.
Paste your full log into the error finder

Was this page helpful?

Anonymous. Only a yes/no counter is stored; no account, IP address or device details.

Sources & references

Localized from the existing Chinese research draft. Original source-check dates are retained; this translation is not new technical verification or a runtime test.

01pip debugSource checked: 2026-09-2102PyTorch local installationSource checked: 2026-09-2103ComfyUI manual installationSource checked: 2026-09-2104pip install package search locationsSource checked: 2026-09-25

Report an issue · 25415188-ea2e-5967-8786-be694a090415