8000 [WIP] Added deprecation warnings for min_impurity_split by FarahSaeed · Pull Request #10174 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]

Skip to content

[WIP] Added deprecation warnings for min_impurity_split #10174

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

Closed
wants to merge 10 commits into from

Conversation

FarahSaeed
Copy link
Contributor

Reference Issues/PRs

Fixes #10158

What does this implement/fix? Explain your changes.

Added deprecation warnings for min_impurity_split in constructor.

The warning message used is the one in tree.py

warnings.warn("The min_impurity_split parameter is deprecated and"
" will be removed in version 0.21. "
"Use the min_impurity_decrease parameter instead.",
DeprecationWarning)

Any other comments?

These are the files I found appropriate for adding min_impurity_split deprecation warnings.

  • forest.py
  • gradient_boosting.py

@amueller
Copy link
Member

This doesn't seem related to #10158. The issue I raised was about catching these warnings when raised by the tests.
We don't usually raise deprecation warnings in __init__ because that's not the only mechanism to set the parameter.

@FarahSaeed
Copy link
Contributor Author

hmm I see ... I'll examine the tests then :)

@FarahSaeed FarahSaeed closed this Nov 21, 2017
@FarahSaeed FarahSaeed deleted the feature branch November 21, 2017 14:45
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.

Enable warnings on travis (and make sure they are reasonable)
3 participants
0