New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENH - make get_next
a regular solver method
#566
Conversation
Do you think it is worth going through a deprecation cycle for this as it is used extensively in benchmarks? Any thoughts @tomMoral @mathurinm? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM up to a nitpick
benchopt/tests/test_benchmarks/dummy_benchmark/solvers/solver_test.py
Outdated
Show resolved
Hide resolved
@Badr-MOUFAD can you add a whatsnew entry before we merge ? |
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## main #566 +/- ##
==========================================
- Coverage 54.14% 54.09% -0.06%
==========================================
Files 43 43
Lines 2833 2834 +1
Branches 517 518 +1
==========================================
- Hits 1534 1533 -1
- Misses 1184 1185 +1
- Partials 115 116 +1 |
This enables accessing solvers parameters and attributes by making
get_next
a regular method instead ofstaticmethod
closes #564