[go: up one dir, main page]

Skip to content
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

MNT Update main-ci lock files #29388

Merged
merged 18 commits into from
Jul 9, 2024
Merged

Conversation

lesteve
Copy link
Member
@lesteve lesteve commented Jul 2, 2024

Take over and close #29276

Summary of the fixes:

Copy link
github-actions bot commented Jul 2, 2024

✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

Generated for commit: aab6025. Link to the linter CI: here

@lesteve
Copy link
Member Author
lesteve commented Jul 2, 2024

Oh well, so it does look like the doc build segmentation fault is a real thing 😱 ...

@lesteve
Copy link
Member Author
lesteve commented Jul 3, 2024

Oh well polars, what else 😅? pola-rs/polars#17380

Seems an issue with polars and numpy 2.

Edit: this is a known polars issue pola-rs/polars#16998 which is waiting for rust-numpy to support numpy 2: PyO3/rust-numpy#429

@lesteve
Copy link
Member Author
lesteve commented Jul 8, 2024

@adrinjalali maybe this is one you could look at, being on triage duties?

I tried to sum up the main differences in the top post to facilitate review. The rest of it is lock-file diff, personally I quickly glance over it making sure the changes are mostly changed versions.

Copy link
Member
@adrinjalali adrinjalali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise LGTM. (And I think @glemaitre and I are switching triage duty since he's on vacation next week)

# - bump minimum matplotlib supported versions to 3.9 at one point
# - complicate the example code to do the right thing depending on
# maplotlib version
"matplotlib": "<3.9",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about fixing the code, so that our code actually runs warning free for people with an up to date env, and ignore those warnings in the min-version of the CI?

Copy link
Member Author
@lesteve lesteve Jul 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And I think @glemaitre and I are switching triage duty since he's on vacation next week

Right, I likely missed the update 😉

what about fixing the code, so that our code actually runs warning free for people with an up to date env, and ignore those warnings in the min-version of the CI?

Fixing the code is the "complicate the example code" option (if matplotlib recent enough use the new way else use the old way) I tried to describe in the comment, maybe let's leave this for a separate PR?

For completeness, this is a DeprecationWarning in matplotlib 3.9:

matplotlib._api.deprecation.MatplotlibDeprecationWarning: The 'labels' parameter of boxplot() has been renamed 'tick_labels' since Matplotlib 3.9; support for the old name will be dropped in 3.11.

3 examples fail (DeprecationWarning turned into error):

  • examples/inspection/plot_permutation_importance_multicollinear.py
  • examples/ensemble/plot_gradient_boosting_regression.py failed
  • examples/release_highlights/plot_release_highlights_0_22_0.py

See build log from one of the commit in this PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I saw the same thing in another library and there we just did the "complicated" thing by having something in fixes.py.

I don't mind having it for a separate PR, but we always have the danger of forgetting to unpin things for a while.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opened #29434 to not forget. In practice, one day or another I would have bumped into this TODO and be annoyed enough to do something about it 😉.

@ogrisel ogrisel merged commit 0dba98f into scikit-learn:main Jul 9, 2024
40 checks passed
@lesteve lesteve deleted the update-main-lock-files branch July 9, 2024 07:33
glemaitre added a commit to glemaitre/scikit-learn that referenced this pull request Sep 9, 2024
glemaitre added a commit that referenced this pull request Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants