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
[SPARK-29381][PYTHON][ML] Add _ before the XXXParams classes #26103
Conversation
Test build #111976 has finished for PR 26103 at commit
|
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.
Would this affect anyone who has subclassed these quasi-internal classes? I'm trying to figure out how likely it is that this breaks someone's extension vs the value. We can break this in 3.0 but just weigh it against how important it is.
Almost all of these quasi-internal classes _XXXParams are newly added in these parity jiras with very few exceptions. One of them is |
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.
Seems OK pending tests.
Test build #4896 has finished for PR 26103 at commit
|
Merged to master |
Thanks a lot! @srowen |
What changes were proposed in this pull request?
Add _ before XXXParams classes to indicate internal usage
Why are the changes needed?
Follow the PEP 8 convention to use _single_leading_underscore to indicate internal use
Does this PR introduce any user-facing change?
No
How was this patch tested?
use existing tests