Don't check duckdb and ray import if not used#33
Merged
Merged
Don't check duckdb and ray import if not used#33
Conversation
Contributor
|
+1 |
yuzelin
added a commit
that referenced
this pull request
Dec 4, 2024
(cherry picked from commit 7f6a1d4)
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.
Purpose
Currently, it will import ray and duckdb even if user doesn't call to_duckdb and to_ray.
If user doesn't install ray/duckdb, an import error will be raised.
This PR fix it.
This new behavior is the same as PyIceberg.
Tests
API and Format
Documentation