Hacker News Reader

It's more an issue of torch not yet providing prebuilt binary wheels for Python 3.11. You could probably get it working, but it would involve building torch from source, which can be rather more involved than 'pip install'.

It's a packaging/release engineering limitation more than a language incompatibility thing.

View on HN

Again (with little understanding) I'd ask a similar question: is there such a huge difference under the skin between Python 3.10 and 3.11 to render a prebuilt binary (torch or otherwise) for 3.10 incompatible with 3.11, on an otherwise identical platform?

The C API for Python changes between major Python versions. This means that native-code extensions (like torch) need to be build specifically for each version of Python they want to support.

Why doesn't torch use automated artifact generation? As in a virtual machine or a github actions that download dependencies and compile it when a new python version is released?

Also using an environment with a different version of python is very easy so it'd be my first solution too.

Reply on news.ycombinator.com