1ffffc1cf1#6579 reworded these comments to attribute the failure to a half-resolved install and claimed a clean 4.14 is fine on 3.13. That is wrong: #6483 is a genuine anyio 4.14 + Python 3.13 regression. 4.14 added a per-task cancel scope in its asyncio backend (TaskHandle/_run_coro) that gets exited in the wrong task under starlette's collapsing task group, raising the cancel-scope RuntimeError on streaming; 4.13 has no such code and is unaffected (the reporter confirmed 4.13.0 fixes it). The TaskHandle ImportError is only the secondary macOS-arm symptom from the mlx-vs-cap version fight. Comments only.
12 lines
666 B
Text
12 lines
666 B
Text
# mlx-vlm / mlx-lm declare transformers>=5.x which conflicts with the
|
|
# main venv's constraints.txt pin transformers==4.57.6 and forces uv to
|
|
# backtrack unsloth. Relax to match the pin -- per-model 5.x routing
|
|
# happens at runtime via the side-car venvs.
|
|
transformers>=4.57.6
|
|
|
|
# mlx-vlm / mlx-lm pull anyio>=4.14, which fights the constraints.txt cap (needed
|
|
# for the 4.14 Python-3.13 streaming cancel-scope RuntimeError, #6483). The -c
|
|
# constraint loses that fight on macOS-arm, leaving a half-resolved 4.14/4.13
|
|
# anyio that also ImportErrors on TaskHandle and 500s the server. An override
|
|
# wins the fight, so force one consistent <4.14 here too.
|
|
anyio<4.14.0
|