4 ms·
Total tangent, but this is something that inrigued me in recent days, after struggling with a similar problem: > You also need Python 3 - I used Python 3.10, a
by mft_ 4y ago
Total tangent, but this is something that inrigued me in recent days, after struggling with a similar problem:
> You also need Python 3 - I used Python 3.10, after finding that 3.11 didn't work because there was no torch wheel for it yet.
Is there a solid reason for denying forwards compatability by default in this manner? I'd faaaar from an expert on the inner workings of Python, but how often does a incrementally newer version (e.g. 3.11 over 3.10) introduce changes which would break module installation or function?
I can see that in some cases, a module taking advantage of newly-introduced features would require limiting backwards compatability, but the opposite?
- SnowflakeOnIce 4y agoIt'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.
- IanCal 4y agoAlso using an environment with a different version of python is very easy so it'd be my first solution too.
- mft_ 4y agoAgain (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?
- SnowflakeOnIce 4y agoThe 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.
- Gravyness 4y agoWhy 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?