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?
> 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?