2025-12-13 09:04:57 +00:00
|
|
|
--extra-index-url https://download.pytorch.org/whl/cu130
|
2025-08-08 20:48:38 +00:00
|
|
|
torch
|
2025-11-27 15:02:48 +00:00
|
|
|
git+https://github.com/huggingface/diffusers
|
2025-08-08 20:48:38 +00:00
|
|
|
transformers
|
|
|
|
|
accelerate
|
|
|
|
|
peft
|
|
|
|
|
optimum-quanto
|
2025-08-09 07:08:35 +00:00
|
|
|
numpy<2
|
|
|
|
|
sentencepiece
|
2025-08-28 08:26:42 +00:00
|
|
|
torchvision
|
2025-11-27 15:02:48 +00:00
|
|
|
ftfy
|
2025-12-13 11:59:03 +00:00
|
|
|
chardet
|
fix(diffusers): drop compel from requirements to unblock pip resolver (#9632)
compel 2.3.1 (latest, Nov 2025) declares transformers~=4.25 in its
metadata, i.e. >=4.25,<5.0. After transformers 5.0 (2026-01-26) and
huggingface-hub 1.0 (2025-10-27) shipped, the weekly DEPS_REFRESH
cache rotation in CI started seeing the new majors and pip's resolver
went into multi-hour backtracking storms walking every transformers
4.x candidate against every accelerate/hf-hub/tokenizers combination
to find a set compel would accept. The 2026-04-29 backend-build for
the diffusers backend (darwin-mps + l4t + cublas13-turboquant matrix
cells) hit the GitHub Actions 6h job timeout still inside pip
install — the build itself never started.
compel is the only hard upper bound on transformers in this stack
(diffusers, accelerate, peft, optimum-quanto are all flexible), and
upstream support for transformers 5 is still in flight: damian0815/
compel#129 ("Modernize Compel for Transformers 5") and #128 ("Bump
transformers version to >5.0") are both open as of today.
backend.py only constructs Compel() when COMPEL=1 is set in the env
(default off), so make compel a true optional extra:
- Wrap the top-level `from compel import ...` in try/except
ImportError, mirroring the existing sd_embed pattern.
- Auto-disable COMPEL with a warning when the module isn't
installed, instead of crashing on module load.
- Drop compel from all eight requirements-*.txt variants so the
resolver no longer has to satisfy its transformers cap.
- Leave a TODO in backend.py and in each requirements file
pointing at the upstream PR/issue, so the dependency can be
reinstated once compel supports transformers >= 5.
Users who rely on weighted-prompt embeddings can opt in with a
manual `pip install compel` alongside COMPEL=1; the warning emitted
on startup tells them how.
Assisted-by: Claude:claude-opus-4-7 [Bash Read Edit WebFetch]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
2026-05-01 12:45:14 +00:00
|
|
|
# TODO: re-add compel once it supports transformers >= 5.
|
|
|
|
|
# Tracking: https://github.com/damian0815/compel/pull/129
|
|
|
|
|
# https://github.com/damian0815/compel/issues/128
|
|
|
|
|
# compel currently pins transformers~=4.25, which forced pip into multi-hour
|
|
|
|
|
# resolver backtracking storms in CI. backend.py imports it lazily and gates
|
|
|
|
|
# the COMPEL=1 env var on the import succeeding, so dropping it here is safe.
|