Open
Conversation
jameslamb
requested review from
StrikerRUS,
borchero,
jmoralez and
shiyu1994
as code owners
Contributor
|
@jameslamb perfect - I can't remember having ever seen this! |
Member
Author
|
Haha yes, thank you. Fixed. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Contributes to #6732
Deprecates
lgb.interprete(), to fix that typo in the interface.The exact same functionality and API is preserved in the package as
lgb.interpret().Notes for Reviewers
This function is not used by anything on CRAN (https://github.com/search?q=org%3Acran%20%22lgb.interprete%22&type=code). One release of deprecation warnings should be sufficient to remove it.
cc @mayer79 just so you're aware (I expect you care about this function)