The new lightly release breaks BaseTask with timm imports about torchgeo HOT 5 CLOSED

For anyone who encounters this issue, the current workaround is:

pip install torchgeo lightly!=1.4.26

It looks like this is going to be fixed in the next lightly release: lightly-ai/lightly#1487

from torchgeo.

Thanks for the bug report! We also noticed this when dependabot tried to update our lightly dependency in #1823. Here is a rundown of how this bug surfaced. It's actually pretty complicated (and interesting!)

The issue started when lightly v1.4.26 added an optional dependency on timm in lightly-ai/lightly#1479. If timm is available, lightly exposes additional parts of the API and imports certain features of timm. However, the features it uses are only available starting in timm v0.9.9: huggingface/pytorch-image-models#1996.

At the same time, TorchGeo depends on segmentation-models-pytorch, which requires timm v0.9.2: https://github.com/qubvel/segmentation_models.pytorch/blob/v0.3.3/requirements.txt#L4. We've asked them many times not to pin to a specific version of timm, but to no avail. The library itself may not even be maintained anymore, there haven't been any updates in quite some time.

So the short-term fix is to pin TorchGeo to depend on lightly<=1.4.25. This will be included in the next TorchGeo patch release, likely some time in the next week. A medium-term fix would be for lightly to first check the version of timm available and only try to use it if it's timm v0.9.9+. I'm not sure if they will be interested in the additional code complexity to check this, but I'll suggest it anyway. A long-term fix would be to somehow resurrect or replace segmentation-models-pytorch so we can finally use modern versions of timm. I'll also explore this, but I won't get my hopes up.

from torchgeo.

This is now fixed in main and will be included in the next release. It's also been fixed in lightly itself (lightly-ai/lightly#1487), so future lightly releases will be fine. We're still considering migrating from smp to torchseg to remove the timm version constraint, which will also alleviate this issue.

from torchgeo.

from torchgeo.

FYI, lightly 1.5.0 has now been released and fixes this bug.

from torchgeo.