-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
MAINT add deprecation for transition to new developer API tools #30299
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
ping @ogrisel @adrinjalali @jeremiedbb This part is quite easy and can be merged without the tags. |
Co-authored-by: Adrin Jalali <[email protected]>
I also think one cycle is enough for these private methods. |
I'm not against this solution. We warn for 1.6, and we remove in 1.7. |
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. Since it's a deprecation of private methods I'm also fine with a 1 release cycle.
Move the version of deprecation to 1.7. Enabling auto-merge. |
…it-learn#30299) Co-authored-by: Adrin Jalali <[email protected]>
Co-authored-by: Adrin Jalali <[email protected]>
Partially address #30298
This PR avoid the breaking changes that we introduced by moving tools and changing the name.
Instead, it raises a deprecation warning to give a bit more time for user to adapt their code.
TODO
_validate_data
_check_feature_name
_check_n_features