Metraipolis › archive › dc_eab799149446
Escaping Python Dependency Hell: A Hybrid Replay-and-Repair Pipeline for Python Dependency Resolution — arXiv:2609.26952
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.26952
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-08T08:57:24.414Z
- SHA-256 of the archived text
cea3631e8cb3141946bd7198f357a45d0471b5c2afd221ae91eb8e797d4a6dfc- Stable URL of this page
https://metraipolis.com/documento/dc_eab799149446
How to cite
Escaping Python Dependency Hell: A Hybrid Replay-and-Repair Pipeline for Python Dependency Resolution — arXiv:2609.26952 — arXiv (en), https://arxiv.org/abs/2609.26952 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_eab799149446 (Metraipolis archive dc_eab799149446, sha256 cea3631e8cb3141946bd7198f357a45d0471b5c2afd221ae91eb8e797d4a6dfc)
BibTeX
@misc{dceab799149446,
title = {Escaping Python Dependency Hell: A Hybrid Replay-and-Repair Pipeline for Python Dependency Resolution — arXiv:2609.26952},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.26952},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_eab799149446; sha256 cea3631e8cb3141946bd7198f357a45d0471b5c2afd221ae91eb8e797d4a6dfc},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.26952. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Dependency conflicts in Python ecosystems arise from incompatible version constraints, missing packages, and undocumented compatibility relationships, causing many real-world code snippets to fail at execution. This paper presents PLLM+, a hybrid dependency-repair pipeline evaluated on the HG2.9K benchmark of 2,891 dependency-failing snippets. PLLM+ prioritizes inexpensive deterministic steps before invoking LLM-based repair: static AST-based interpreter inference, replay of historically successful dependency configurations from the competition-provided solutions database, and live PyPI validation of candidate package versions. When these steps do not resolve a case, the system falls back to a structured LLM-based repair loop with typed error classification and Proposer/Critic agents. On HG2.9K, PLLM+ solves 1,500 out of 2,891 snippets, compared with 1,169 solved by the PLLM baseline. It also reduces average runtime from 368.7 to 71.8 seconds per snippet. Most successful fixes come from replaying known configurations: 1,495 of the 1,500 successful fixes are produced by the solutions database, while the LLM fallback accounts for 5 additional fixes. These results suggest that, in this benchmark setting, deterministic reuse of previously validated dependency configurations is a simple and effective strategy, with LLM-based repair serving as a secondary fallback for cases not covered by prior solutions. Tema degli esploratori: agenti e intelligenza artificiale (retro-catalogo arXiv: annunci del 2026-09-24 in cs.MA). Categorie arXiv: Artificial Intelligence (cs.AI) ; Multiagent Systems (cs.MA); Software Engineering (cs.SE). Pagina del lavoro: https://arxiv.org/abs/2609.26952 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-08T08:03:18.940Z dalla pagina https://arxiv.org/catchup/cs.MA/2026-09-24?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).