python
install_error
ai_generated
true
ERROR: Could not install packages due to an EnvironmentError: [Errno 2] No such file or directory: '.../egg-info/PKG-INFO'
ID: python/pip-egg-info-missing-metadata
80%Fix Rate
85%Confidence
0Evidence
2024-03-15First 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's setup.py or setup.cfg references egg-info metadata that was not generated, often due to a missing setup() call or incorrect build backend configuration.
generic中文
包的setup.py或setup.cfg引用了未生成的egg-info元数据,通常是由于缺少setup()调用或构建后端配置错误。
Workarounds
-
85% success
Ensure setup.py has a proper setup() call: `python setup.py egg_info` to pre-generate metadata, then pip install .
-
90% success
Switch to pyproject.toml with setuptools.build_meta: `[build-system] requires = ["setuptools"] build-backend = "setuptools.build_meta"` and run pip install .
-
75% success
Clean rebuild: `rm -rf *.egg-info build dist && pip install --no-cache-dir .`
Dead Ends
Common approaches that don't work:
-
95% fail
pip will overwrite or ignore manually created files, and the underlying metadata generation process is still broken.
-
70% fail
This bypasses isolated build environments but doesn't fix the fundamental setup.py issue; the error persists if setup.py is malformed.
-
60% fail
If the build backend doesn't regenerate it properly due to configuration errors, deletion alone won't solve the problem.