cd /news/ai-research/escaping-python-dependency-hell-a-hy… · home topics ai-research article
[ARTICLE · art-138803] src=arxiv.org ↗ pub= topic=ai-research verified=true sentiment=↑ positive

Escaping Python Dependency Hell: A Hybrid Replay-and-Repair Pipeline for Python Dependency Resolution

A hybrid dependency-repair pipeline called PLLM+ solved 1,500 of 2,891 dependency-failing Python snippets on the HG2.9K benchmark, up from 1,169 solved by the PLLM baseline, according to an arXiv paper (2609.26952v1). PLLM+ cut average runtime from 368.7 to 71.8 seconds per snippet by prioritizing deterministic steps — static AST-based interpreter inference, replay of historically successful dependency configurations, and live PyPI validation — before falling back to a structured LLM repair loop with typed error classification and Proposer/Critic agents. Replaying known configurations from the competition-provided solutions database produced 1,495 of the 1,500 successful fixes, with the LLM fallback accounting for only 5.

by read1 min views1 publishedSep 24, 2026

arXiv:2609.26952v1 Announce Type: new Abstract: 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.

── more in #ai-research 4 stories · sorted by recency
── more on @pllm+ 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/escaping-python-depe…] indexed:0 read:1min 2026-09-24 ·