-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
MNT Clean-up deprecations for 1.7: TSNE's n_iter #31140
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
Merged
lesteve
merged 1 commit into
scikit-learn:main
from
jeremiedbb:cln-deprecations-1.7-tsne
Apr 9, 2025
+5
−64
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 message below says:
# Also make sure to change `max_iter` default back to 1000 and deprecate None
This removes
None
straight away and doesn't deprecate it, right?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.
Yes but this is not how we do it usually. We've decided that when we add
None
as a valid option for a deprecation, then we can remove it right away at the end of the deprecation. It's not like it's a meaningful option, just a sentinel during deprecation.The writer of the message must have not been aware of this, but it's alright to do it anyway.
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.
OK my main point was that in scikit-learn 1.6.1 the following code does not give any warning and in 1.7 this is going to break (with this PR merged):
I guess that's OK because it's unlikely that someone has used
max_iter=None
explicitly?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.
indeed, we never encouraged to set None explicitely. It's there only to serve as a sentinel while we have the 2
max_iter
andn_iter
params. We already merged several PRs like this one for 1.7 and and before 1.6 as well.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.
This make sense @jeremiedbb. So I guess this review comment can be resolved?