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.
23 lines
684 B
Text
23 lines
684 B
Text
# Single-env pins for unsloth + studio + data-designer
|
|
# Keep compatible with unsloth transformers bounds.
|
|
transformers==4.57.6
|
|
trl==0.23.1
|
|
huggingface-hub==0.36.2
|
|
|
|
# Studio stack
|
|
datasets==4.3.0
|
|
pyarrow==23.0.1
|
|
|
|
# FastMCP/OpenEnv compat
|
|
fastmcp>=3.0.2
|
|
mcp>=1.24,<2
|
|
websockets>=15.0.1
|
|
|
|
# Cap anyio <4.14: 4.14's new asyncio per-task cancel scope (TaskHandle/_run_coro)
|
|
# gets exited in the wrong task on Python 3.13 under starlette's collapsing task
|
|
# group, raising "RuntimeError: ... exit a cancel scope that isn't the current
|
|
# task's" on streaming responses (#6483); 4.13 has no such code. Global cap so
|
|
# later with-deps steps can't re-resolve it up.
|
|
anyio<4.14.0
|
|
|
|
pandas==2.3.3
|