eli-schwartz commented on issue #36411: URL: https://github.com/apache/arrow/issues/36411#issuecomment-4308433821
> The current build system of pyarrow consists of using setuptools with a custom `setup.py` that calls cmake to do the actual build. While this works, there are nowadays newer python "build backends" that we could benefit from to make this easier to maintain and use. As far as I can tell, none of the mission objectives from this ticket are harmed in any way by the continued presence of the setuptools package as an internal dependency of the git version generator utility program. Pyarrow does now, indeed, have an improved build process that is marketed as easier to maintain than a setup.py file. Why should pyarrow refrain from using setuptools_scm just because internally it depends on setuptools? -- 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]
