Skip to content

fix(deps): use a floor pin for safetensors so fresh installs resolve - #9

Open
rakhimovv wants to merge 1 commit into
boundless-large-model:mainfrom
rakhimovv:fix/safetensors-floor-pin
Open

fix(deps): use a floor pin for safetensors so fresh installs resolve#9
rakhimovv wants to merge 1 commit into
boundless-large-model:mainfrom
rakhimovv:fix/safetensors-floor-pin

Conversation

@rakhimovv

Copy link
Copy Markdown

Fixes #8.

requirements.txt is installed after pip install diffsynth==2.0.11, so its exact pin safetensors==0.7.0 downgrades the version that the diffsynth dependency chain had just resolved. diffsynth declares transformers with no upper bound, and transformers raised its floor to safetensors>=0.8.0 in 5.13.0 (2026-07-03), enforced at import time. The result is that a fresh install following the README fails on import diffsynth:

ImportError: safetensors>=0.8.0 is required for a normal functioning of this module, but found safetensors==0.7.0.

This changes the exact pin to a floor, which lets pip satisfy both constraints and keeps working if transformers raises its floor again.

Safe for this codebase: safetensors 0.8.0's breaking change is limited to the low-level serialize / serialize_file API, while this repo and diffsynth only use the read path (from safetensors import safe_open).

Verified on Linux / 4xH100 / CUDA 12.8, Python 3.10.21, torch 2.8.0+cu128:

  • pip install resolves cleanly (safetensors-0.8.0, transformers-5.15.0); pip check reports no broken requirements.
  • bash scripts/infer_example.sh runs to completion on all three demo/demo.jsonl episodes, producing outputs/inference/episode{0,1,2}.mp4.

diffsynth 2.0.11 declares transformers without an upper bound, and
transformers raised its safetensors floor from >=0.4.3 to >=0.8.0 in
5.13.0. Because requirements.txt is installed last, the exact pin
safetensors==0.7.0 downgraded the version installed by the diffsynth
dependency chain, making `import diffsynth` fail with an ImportError.

A floor pin lets pip satisfy both constraints, and keeps working if
transformers raises its floor again.
@rakhimovv
rakhimovv force-pushed the fix/safetensors-floor-pin branch from 12cf6f7 to a558e15 Compare September 1, 2026 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

requirements.txt pin safetensors==0.7.0 breaks a fresh install (conflicts with transformers>=5.13)

1 participant