Skip to content

Add Python 3.14 support and move to torch 2.14 with CUDA 13. - #1194

Merged
kevinzakka merged 1 commit into
mainfrom
py314-torch
Sep 27, 2026
Merged

kevinzakka merged 1 commit into
mainfrom
py314-torch

Conversation

@kevinzakka

Copy link
Copy Markdown
Collaborator

Adds Python 3.14 support and moves to torch 2.14, which clears the remaining torch Dependabot alerts. PyTorch no longer publishes cu128 wheels past 2.11, so the cu128 extra is replaced with cu130; training now needs driver 580+.

@kevinzakka kevinzakka mentioned this pull request Sep 27, 2026
@kevinzakka
kevinzakka merged commit 4ac9df2 into main Sep 27, 2026
22 checks passed
@kevinzakka
kevinzakka deleted the py314-torch branch September 27, 2026 21:23
vestoriabot added a commit to vestoriaai/mmjlab that referenced this pull request Sep 30, 2026
`run_train` hard-coded `device="cpu"` whenever CUDA was not requested,
leaving Apple Silicon users no path to GPU-accelerated policy training.
Mirror the CUDA branch's auto-detection style: with no CUDA devices,
pick `mps` when `torch.backends.mps.is_available()`, else `cpu`.

MuJoCo physics stays on CPU in that case: the classic backend requires
a CPU device and MuJoCo Warp has no Metal backend, so only policy
inference/learning runs on MPS. On YAM lift-cube (vision, 64 envs) this
cuts iteration time 20.4s -> 2.1s (~10x); pure-MLP tasks are ~2x slower
on MPS than CPU, so CPU remains preferable there.

Motivated by Apple Silicon training support; upstream mujocolab#1194's move to
torch 2.14 keeps MPS a first-class torch target going forward.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@saikishor

Copy link
Copy Markdown
Contributor

@kevinzakka is there a way to also add support for CUDA 12 alongside? Some server-side GPUs still maintain CUDA 12 and do not support CUDA 13 yet, and this'll create a problem for us to bump mjlab versions in the future.

Do you see a possibility?

@kevinzakka

Copy link
Copy Markdown
Collaborator Author

Hi @saikishor, can you open an issue so I can track it?

@saikishor

Copy link
Copy Markdown
Contributor

Hi @saikishor, can you open an issue so I can track it?

Sure thing. I'll create it as soon as I get access to my PC. Thank you

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.

2 participants