# WARNING: The candidate selected for download or install is a yanked version: 'mypkg' candidate (version 2.0.0 at https://.../mypkg-2.0.0-py3-none-any.whl (from https://pypi.org/simple/mypkg/))
Reason for being yanked: <none given>

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

## Root Cause

A pinned version in requirements.txt was yanked on PyPI, but pip still resolves it because the pin explicitly requests that exact version.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 3.x | active | — | — |

## Workarounds

1. **** (98% success)
   ```
   Edit requirements.txt to mypkg==2.0.1 (or >=2.0.1,<3) and re-run pip install -r requirements.txt.
   ```
2. **** (90% success)
   ```
   Run pip-audit or pip index versions mypkg to list available versions and identify yanked ones.
   ```

## Dead Ends

- **** — Cache is not the reason the yanked version was selected. (90% fail)
- **** — Still resolves to the same yanked version. (88% fail)
- **** — Older pip silently installs yanked versions, hiding the problem. (80% fail)