[breaking] Remove dask from the default import. - #10935
Merged
Merged
Conversation
wphicks
reviewed
Oct 29, 2024
wphicks
left a comment
Contributor
There was a problem hiding this comment.
Is the primary goal here code simplification through elimination of lazy loading?
Member
Author
|
@wphicks For both simplification with consistency with the spark package. |
wphicks
approved these changes
Oct 29, 2024
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.
This aligns with the spark package and simplifies the imports significantly. We will work on improved learning to rank support and basic resilience.
This is a breaking change as:
will stop working. One needs to import the dask module independently: