Open ivelin opened 7 months ago
Hi @ivelin, and thanks for raising this issue.
It's true that we are still relying on pytorch-lightning
rather than lightning
.
I think it would be a good point for us to also start migrating to lightning
. It shouldn;t be too much of an effort.
I'll add a ticket for this and put it into the backlog.
As you said, for now I'd suggest to use optuna<=3.4.0.
Thank you for clarifying, @dennisbader . That may help in the future with compatibility with other libraries in the torch ecosystem. Looks like the pytorch lightning team is steadily pushing in that direction.
It's true that we are still relying on
pytorch-lightning
rather thanlightning
.
Both packages shall have identical codebases for the same version, but it is true that inheritance and some internal checks may complain when a particular class is imported from an alternative package than Trainer...
Describe the bug When using Darts with Optuna 3.5, there are errors due to the fact that Optuna switched to
pip lightning
andimport lightning.pytorch
while darts still usespip pytorch-lightning
andimport pytorch_lightning
To Reproduce
Expected behavior Darts and Optuna should be able to coexist while both depending on Pytorch Lightning.
System (please complete the following information):
Additional context I was able to work around the problem by downgrading optuna to 3.4.0 which is the version before they switched to
pip lightning
andimport lightning.pytorch