[FEATURE] Python 3.11 support

[adamjstewart]

Is your feature request related to a problem? Please describe.

PyTorch 2.0 was released yesterday, adding Python 3.11 support. However, the latest release of timm does not yet support Python 3.11 (#1530).

Describe the solution you'd like

I hate to be that guy, but could we get a new release soon that includes #1649 so we can use Python 3.11? Apologies if a new release is already being planned, I don't want to rush you.

Describe alternatives you've considered

Alternative is Python 3.10.

Additional context

We're trying to update TorchGeo to Python 3.11 (microsoft/torchgeo#1180), but rely on timm for its amazing models, so we're stuck until there's a new release.

[rwightman]

@adamjstewart pip install --pre timm should give you a release that works with python 3.11, I've tried it but back to 3.10 because 3.11 isn't fully supported by pytorch (ie torch.compile doesn't work). Working towards getting it out of pre-release (I need deprecation mappings/warmings of a number of models that have changed names since adding multi-weight & HF hub support).

[rwightman]

I could push a new 0.6 w/ that fix but was hoping to get more users on 0.8.x

[adamjstewart]

Thanks, I didn't realize there were already pre-releases available. However, we're also using segmentation-models-pytorch, which pins its timm dependency to exactly 0.6.12. I can probably convince them to upgrade to 0.6.13 and hopefully relax the "must be this exact version" constraint, but it would be much harder to convince them to pin to a pre-release version. So I think a 0.6.13 version makes sense unless 0.8.0 is close to having an official stable release.

[adamjstewart]

segmentation-models-pytorch is ready to update to the latest version of timm whenever it gets released. I think a 0.6.13 version makes sense if 0.8.x isn't ready yet.

[rwightman]

@adamjstewart getting closer on 0.8 (will transition to 0.9 for next stable I think), but still a few models and deprecation mappings to transition before I'm ready. I just pushed a 0.6.13 with the Python 3.11 change, if any other 3.11 issues come up let me know...

[adamjstewart]

Thanks for the release! I'll try to convince segmentation-models-pytorch to bump versions now.