Is there a Python Upgrade coming?

[Profileiche]

I was okay with SM lagging behind in its Python version when I installed FaceID and the likes, and the 3.10 made it harder than necessary. But with video generation on local, SM now hinders to use things like sageattention from working. Is there any intention to upgrade the underlying python version?

[mohnjiles]

Yep, once 2.14 releases (soon ™️) that's our top priority for the next release. Internally we have a version with 3.10.16 working. Plan is to let you choose between a few different versions, probably in the 3.10 - 3.12 range.

[Profileiche]

I am looking forward to it! Thank you for the update... on the update 😇

[joshistoast]

It's now 2.15.3 and python 3.10.11 is the only version showing despite toggling "show unsupported python versions".

[EriIaz]

For the lack of a better thread @mohnjiles

It is relevant
For the same reason we're facing issues with torch2.8.0+cu1.2.8.
Nobody tests Forge Neo with Python 3.13.5. Nobody in their team navigates the dependency hell for that specific build.
Yes, 3.13.5 works for the time being. No, that doesn't mean it's not going to break out of nowhere further down the line. It works until it doesn't. A1111's original UI used to be sensitive to stuff like that, best practice was to use exactly what the author suggested to use.
That's why I am pointing out that out. 3.13.12 build is what the Forge Neo devs are responsible for. If that breaks, they owe us a fix, and it won't be on the Matrix team.

[mohnjiles]

It was not relevant, as others have pointed out, just selecting Python 3.13 doesn't fix this on its own. We're updating the install script as well since things have changed there too. So yes, we're aware of the issue, including the recommended Python version from the Forge Neo authors (I read the readme too). We are actively working on a fix. Every minute spent responding to these threads is one not spent on the actual fix, so I'd appreciate some patience here.

If you want to try things sooner, the available Python versions are tied to the version of uv currently installed — you can grab the latest v0.9.x release from here and replace the one in your <sm_folder>/Assets/uv. That said, it doesn't seem like any 3.13 version fixes the install on its own, so best of luck.

Also, please open a new issue or discussion in the future instead of resurrecting an old thread. Thanks!