WillAyd commented on issue #36411: URL: https://github.com/apache/arrow/issues/36411#issuecomment-2770519262
Thank you to everyone that has been reviewing the reference PR for a meson-python integration. I think its in a good spot structure wise, so I figured it's worth cycling back here with what we've found. Some things that Meson does really well in the context of PyArrow is: - Provides a Python-like syntax, that is likely easier for Python developers with little or no C/C++ knowledge to work with - Does not require Arrow C++ to move away from CMake; there are some tweaks we could make to improve interoperability, but it doesn't all need to be done at once - Provides a solid ecosystem in the scientific Python community, as it is already used by NumPy, SciPy, pandas, etc...It is also the build system in use by arrow-nanoarrow's Python wrapper Some things where Meson is less than ideal: - It does not read environment variables, which are used heavily in our current CI configuration - It would require Arrow C++ developers (who are likely already familiar with CMake) to know Meson as well - It is more opinionated than CMake; straying from the opinionated approach can be challenging (ex: environment variable usage) @raulcd @pitrou @kou please add any thoughts as well -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
