Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

unclecode-litellm shadows the upstream litellm package; the quarantine that motivated the fork has been lifted

Abierto
  • ¿Algo no está bien?
#2,098 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
python
Área
build-system

Línea de trabajo

Inspect the package dependency declaration and the existing [tool.uv] configuration first, then reproduce an environment containing crawl4ai alongside upstream litellm. Confirm the selected dependency direction avoids the shared litellm package collision and that installation from package metadata succeeds without the _redact_string import error.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Follow-up to #1864, where the unclecode-litellm fork was adopted. The emergency that
motivated it has passed, and the fork now costs downstream users something it did not
cost back then.

The fork's premise no longer holds

When #1864 was filed, PyPI had quarantined the entire litellm package — every
version was uninstallable, so pinning a fork was the only way to keep pip install crawl4ai working.

That is no longer the case. On PyPI today:

  • litellm latest is 1.93.0
  • 1.82.7, 1.82.8, 1.82.9 are gone — exactly the compromised releases
  • 1.82.6 and everything from 1.83.0 onward are present and installable

The quarantine was lifted and only the bad releases were removed.

What the fork costs now

crawl4ai 0.9.2 requires unclecode-litellm==1.81.13, which installs a top-level
litellm package — the same import name shipped by the upstream distribution. An
environment that needs both ends up with two different versions written into one
site-packages/litellm/, and which files survive is decided by install order rather
than by either project.

Nothing errors at install time. It surfaces later as:

ImportError: cannot import name '_redact_string' from 'litellm._logging'

The same dependency pair passed on one CI run and failed on another two minutes later,
with nothing changed but resolution order. Because the two distributions have different
names, pip and uv see no conflict to report — they install both, and one silently
overwrites the other's files.

This is not fixable downstream. A [tool.uv] override-dependencies entry works for a
source install, but overrides are not recorded in wheel metadata, so anyone installing
a dependent package from PyPI resolves crawl4ai's requirements directly and hits the
collision again.

Suggested fix

Return to upstream litellm with a floor that excludes the compromised window:

litellm>=1.83.0

1.83.0 is the first release after the three removed versions, so the floor cannot
resolve to a compromised build even if one were ever restored. This keeps pip install crawl4ai exactly as it is today — full package, LLM support included, no extras to
remember — while removing the shadowing.

If there is a reason to stay on the fork, the collision can also be resolved by having
it install as unclecode_litellm and importing it under an alias:

import unclecode_litellm as litellm

Same outcome for crawl4ai users, and the fork stops occupying a name it doesn't own.

A third option, if the fork is meant as a global drop-in replacement: publish the
crawler half as its own distribution (crawl4ai-core or similar), leaving crawl4ai
as the full LLM-enabled package most people install.

Happy to send a PR for whichever direction you prefer.

Lenguaje dominante
Python
Estrellas
84.5k
Forks
8.7k
Merge medio
3 d 9 h
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de unclecode/crawl4ai

Todos los issues de unclecode/crawl4ai

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.