[WIP] Make pyarrow and msgpack optional #8218
Closed
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.
CATEGORY
Choose one
SUMMARY
Makes msgpack and pyarrow dependency optional.
Follow up to the #8069
Some context, we use bazel @ dropbox and bazelyfing pyarrow is quite challenging due to the a bit messy build there e.g. shelling out to cmake.
It would be great to keep not only functionality but also pip dependency optional as well. Please let me know what you think.
REVIEWERS