# ERROR: file:///path/to/project does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.

- **ID:** `python/pip-setup-py-not-found`
- **Domain:** python
- **Category:** install_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

pip was pointed at a directory (or VCS URL) that lacks the build metadata files it needs to identify a Python package.

## Version Compatibility

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

## Workarounds

1. **** (95% success)
   ```
   Point pip at the actual package directory that contains setup.py or pyproject.toml, or install from the parent with `pip install ./project`.
   ```
2. **** (90% success)
   ```
   If the project uses only setup.cfg, add a minimal pyproject.toml: `[build-system]\nrequires=['setuptools>=61']\nbuild-backend='setuptools.build_meta'`.
   ```

## Dead Ends

- **** — Skipping deps does not change the metadata discovery step; the same error is raised. (90% fail)
- **** — The error is about the target directory, not the pip version. (95% fail)