-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
MAINT Require meson-python >= 0.16 and remove temporary work-arounds #29081
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
Conversation
The failures are likely a behaviour change in Pytest 8, likely this one from https://docs.pytest.org/en/8.0.x/changelog.html#other-breaking-changes:
Similar Pytest 8 tweaks were already done in #28318, I need to remember what this was all about 😉. |
Yet another instance of #28820 in the no-OpenMP build, I restarted the build:
|
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.
The changes in test_logistic
seem unrelated
They are actually related in a slightly roundabout way, by updating meson-python we can use Pytest 8 (i.e. remove the |
Weird that the CI didn't fail previously on the FutureWarning... To be consistent with other tests please decorate the test with the following instead
|
assert lr.n_iter_[0] == max_iter | ||
|
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.
We should keep that though
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.
Oops indeed, fixed
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
In #28040 we used some work-arounds that are no longer necessary after meson-python 0.16 release (released 17 April 2024), in particular thanks to mesonbuild/meson-python#569.
I am undecided about removing
sklearn._BUILT_WITH_MESON
. It was previously used to skip a test due to a Meson editable install limitation.sklearn._BUILT_WITH_MESON
is not used anymore in this PR, but you never know, it might be handy for troubleshooting user issues at least until we drop setuptools support?For more details, the code for
sklearn._BUILT_WITH_MESON
isscikit-learn/sklearn/meson.build
Lines 147 to 157 in 6a18882
scikit-learn/sklearn/__init__.py
Lines 142 to 148 in 6a18882