Dependency Conflicts Between unsloth, unsloth_zoo, torch, triton, and transformers in Python 3.10 Environment #2349
Unanswered
MinaArzaghi
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm setting up
unslothandunsloth_zooin a clean environment usingPython 3.10anduv, and ran into several dependency conflicts:unsloth-zoo==2025.3.11requirestriton >= 3.0.0, buttorch==2.2.2strictly requirestriton==2.2.0. This creates a direct conflict betweenunsloth-zooandtorch.unsloth-zoo==2025.3.17introduces version constraints ontransformers:Only allows transformers >= 4.46.1, < 4.47.0 or > 4.47.0This explicitly excludes
transformers==4.47.0, which is the version whereCompileConfigwas introduced — required by recent unsloth code. This leads to an incompatibility in environments wheretransformers==4.47.0is needed.The latest commit on the main branch of
unsloth_zooraises aSyntaxError:SyntaxError: non-default argument follows default argument in UnslothGKDTrainer.py (line 625)This breaks initialization of FastLanguageModel.
Attempts to roll back to earlier commits of
unsloth_zoofailed because specific commits were either missing, untagged, or incompatible withunsloth==2025.3.13.It’s currently unclear which combination of
unsloth, unsloth_zoo, torch, triton, transformers, and peftare officially supported and stable. uv's strict resolver makes these conflicts visible and reproducible.Would be helpful to have an officially supported compatibility matrix or lockfile to avoid these issues.
Beta Was this translation helpful? Give feedback.
All reactions