andygrove opened a new issue, #635: URL: https://github.com/apache/arrow-ballista/issues/635
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** I was chatting with @yahoNanJing, and he asked about moving the Python bindings to a separate repo. I support this if that is what the other maintainers want. ## Pros - Core Ballista can move faster because it will just require Rust knowledge - Makes it easier for the Python bindings to re-use the datafusion-python create, which has a different release schedule than DataFusion core ## Cons - There is a risk that the Python bindings become unmaintained - This creates additional work for creating releases - It makes it less likely that Ballista will be a compelling solution for Python users **Describe the solution you'd like** **Describe alternatives you've considered** **Additional context** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
