python
install_error
ai_generated
partial
DEPRECATION: Legacy setup.py install is deprecated. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of <pkg> or contact the author to suggest that they release a PEP 517 build backend.
ID: python/pip-egg-info-deprecated-setup-py
80%Fix Rate
84%Confidence
0Evidence
2024-02-01First Seen
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| 3.8 | active | — | — | — |
| 3.9 | active | — | — | — |
| 3.10 | active | — | — | — |
| 3.11 | active | — | — | — |
| 3.12 | active | — | — | — |
Root Cause
The package ships only a legacy `setup.py` without `pyproject.toml`, so pip must invoke `setup.py install` instead of a PEP 517 backend.
generic中文
该包仅提供旧式 `setup.py` 而缺少 `pyproject.toml`,因此 pip 必须调用 `setup.py install` 而非 PEP 517 后端。
Workarounds
-
85% success
Pin a version that has migrated to pyproject.toml, or vendor the source and add a minimal pyproject.toml with `[build-system] requires=['setuptools>=61'] build-backend='setuptools.build_meta'`.
-
70% success
Silence locally with `PYTHONWARNINGS=ignore::DeprecationWarning` for CI noise only (does NOT fix the underlying issue).
Dead Ends
Common approaches that don't work:
-
85% fail
The deprecation is about the missing PEP 517 metadata, not build isolation.
-
60% fail
If the upstream project has not yet migrated, the newest release still triggers the same deprecation.