Add version constraint for Optuna

[himkt]

See #2162 for more information.

Motivation

This PR updates the version constraint of Optuna to avoid installing the next major version of Optuna.
See also 🔗 #2162

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

(How should this PR be tested? Do you require special setup to run the test or repro the fixed bug?)

Related Issues and PRs

#2162

[Jasha10]

Thanks very much for letting us know about the upcoming Optuna API changes!
Once Optuna 3.0 is released, we can upgrade this sweeper to use the new API.

[jieru-hu]

could you keep the "optuna>=2.10.0" in the meanwhile?

[himkt]

So you mean it's enough to track the issue #2162 and not necessary to constrain the version, right? It will show warning messages for users when Optuna v3 is available. Is it OK?

[Jasha10]

Just throwing this out there: using multiple constraints on the version should be legal:

    install_requires=[
        ...
        "optuna >= 2.10.0, < 3.0.0",
        ...

The downside of pinning Optuna < 3.0 is that users would not be able to access new Optuna features. Jieru, is that why you were concerned about the pin?

[jieru-hu]

sorry for the confusion, i should have provided more context. I meant "optuna >= 2.10.0, < 3.0.0"

the current impl assumes the version is >=2.10.0 so it'd be great to keep that still

[himkt]

Thank you @Jasha10 and @jieru-hu, it makes sense! Sorry for my poor understanding. 4b39011 restore the lower constraint. 🙋

[jieru-hu]

thank you @himkt!