Skip to content

Update to sklearn 1.8#872

Merged
ArturoAmorQ merged 13 commits into
INRIA:mainfrom
SebastienMelo:sklearn-1.8
Jul 17, 2026
Merged

Update to sklearn 1.8#872
ArturoAmorQ merged 13 commits into
INRIA:mainfrom
SebastienMelo:sklearn-1.8

Conversation

@SebastienMelo

Copy link
Copy Markdown
Collaborator

Do not merge, I still need to check if the jupyter preview works correctly

@ArturoAmorQ

Copy link
Copy Markdown
Collaborator

Thanks for the PR @SebastienMelo! In principle the jupyter-book build in the CI was fixed in #873. You just have to merge main for it to work.

ArturoAmorQ and others added 3 commits January 21, 2026 13:54
* MNT Bump jupyter-book version

* Pin jupyter-book<2.0 instead

* Iter

---------

Co-authored-by: ArturoAmorQ <arturo.amor-quiroz@polytechnique.edu>
Comment thread python_scripts/parameter_tuning_grid_search.py Outdated
@SebastienMelo

Copy link
Copy Markdown
Collaborator Author

All checks have been done. The wrap up quizzes work too.

@ArturoAmorQ ArturoAmorQ left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Other than the improvements in the html representation of estimators, v1.9 did not bring any impact to the course material. We can use this PR to directly target such version.

Otherwise this PR is good to go :) Thanks @SebastienMelo!

Comment thread requirements-dev.txt Outdated
Comment thread requirements.txt Outdated
Comment thread local-install-instructions.md
Comment thread environment.yml Outdated
Comment thread environment-dev.yml Outdated
Co-authored-by: Arturo Amor <86408019+ArturoAmorQ@users.noreply.github.com>
@ArturoAmorQ ArturoAmorQ changed the title Update to sklearn 1.8 Update to sklearn 1.9 Jul 17, 2026
This reverts commit 9abf212.
@ArturoAmorQ ArturoAmorQ changed the title Update to sklearn 1.9 Update to sklearn 1.8 Jul 17, 2026
@ArturoAmorQ

Copy link
Copy Markdown
Collaborator

I decided to keep the scope of this PR to v1.8, as v1.9 introduced behavior changes in DecisionBoundaryDisplay, so it's worth it's own PR and is left as future work.

@ArturoAmorQ ArturoAmorQ left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Let's rather fix to strictly 1.8 to avoid the problem with DesicionBoundaryDisplay

Comment thread environment.yml Outdated
Comment thread requirements-dev.txt Outdated
Comment thread requirements.txt Outdated
Comment thread environment-dev.yml Outdated
Co-authored-by: Arturo Amor <86408019+ArturoAmorQ@users.noreply.github.com>
@ArturoAmorQ
ArturoAmorQ merged commit 0558f34 into INRIA:main Jul 17, 2026
2 of 3 checks passed
github-actions Bot pushed a commit that referenced this pull request Jul 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants