-
Notifications
You must be signed in to change notification settings - Fork 228
[MRG] API: remove num_labeled parameter #119
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
[MRG] API: remove num_labeled parameter #119
Conversation
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. Maybe wait for @perimosocordiae to confirm that we did not miss an important use case for num_labeled
We should probably record these kind of breaking changes in a change log? |
I think the _Supervised classes are introduced in this next 0.4.0 release though? |
My mistake it looks like they were introduced in 0.3.0 (albeit without doc)... |
# Conflicts: # metric_learn/itml.py # metric_learn/lsml.py # metric_learn/mmc.py # metric_learn/sdml.py
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.
Looks good. The original design was mostly for convenience when testing an algorithm: set num_labeled
to 50% of the total, then score against the full set. It's not that useful for general users, so I'm happy to remove it.
I'll mark this for the 0.5 compatibility-breaking release.
I just added deprecation warnings in case we would want to put this in v0.4.0 |
For this a deprecation warning is probably good to have: it is simple (parameter is removed, default behavior does not change) and it is about the supervised metric learning algorithms (whose API should not change much in 0.5.0 except for this). |
Except for the merge conflicts we should be able to merge this now? |
…led_parameter # Conflicts: # metric_learn/itml.py # metric_learn/lsml.py # metric_learn/mmc.py
Yes I think so, I tried to resolve the conflicts but my branch was not updated so I messed it up :p I will try again... |
Seems like rebase was done incorrectly/unsuccessfully? At least from a quick glance it seems like |
Yes indeed, I think I did a bad revert, I'll revert try revert the revert d6bd0d4 |
OK now there's just some tests for NCA that I don't understand why they are here... |
Oups, it appears I deleted it in the big merge #139 (cf. 23d0746#diff-1d435b5cb210c40bb6a7261667f5c5acL138) |
Here is the PR that we should merge (as soon as tests pass): #143 |
I also checked in the diff of #139 for other wrong deletions and it was the only one |
there just remains one error of version to update and it should be OK |
still 1 failure ;-) |
Turns out I used the function |
It should be good to merge now :p |
Fixes #118