# WARNING: The candidate selected for download or install is a yanked version: 'foo' candidate (version 1.2.3 at https://.../foo-1.2.3-py3-none-any.whl)
Reason for being yanked: broken build

- **ID:** `python/pip-yanked-version-installed`
- **Domain:** python
- **Category:** install_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

The maintainer yanked a release on PyPI; pip still installs it if it is the only version satisfying constraints, but warns loudly.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 3.9 | active | — | — |
| 3.10 | active | — | — |
| 3.11 | active | — | — |
| 3.12 | active | — | — |

## Workarounds

1. **** (90% success)
   ```
   Pin to a non-yanked version:
  pip install 'foo==1.2.2'
Or allow any non-yanked:
  pip install 'foo!=1.2.3'
   ```
2. **** (90% success)
   ```
   Check available versions:
  pip index versions foo
Then choose the latest non-yanked release.
   ```

## Dead Ends

- **** — Upgrade only moves to a newer version if one is available; if the yanked release is the only match, the warning persists. (60% fail)
- **** — That flag controls script location warnings, not yanked-version warnings. (95% fail)