You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given CMake's widespread adoption and its advantages in cross-platform compatibility and project configurability, along with Meson's modern and user-friendly design, I'm wondering why they haven't been considered for Pandas. Are there specific technical challenges or historical reasons that have led to the current preference for setuptools and distutils?
Understanding the rationale behind this decision could provide insights into the development philosophy of Pandas and potentially open up discussions on alternative build systems for the project.
The text was updated successfully, but these errors were encountered:
This was discussed back in PDEP-0002. You can see all the reasoning there directly, but at a high level much of the scientific Python community uses Meson
Research
I have searched the [pandas] tag on StackOverflow for similar questions.
I have asked my usage related question on StackOverflow.
Link to question on StackOverflow
https://stackoverflow.com/questions/78334240/why-doesnt-pandas-use-cmake-as-its-build-system
Question about pandas
Given CMake's widespread adoption and its advantages in cross-platform compatibility and project configurability, along with Meson's modern and user-friendly design, I'm wondering why they haven't been considered for Pandas. Are there specific technical challenges or historical reasons that have led to the current preference for setuptools and distutils?
Understanding the rationale behind this decision could provide insights into the development philosophy of Pandas and potentially open up discussions on alternative build systems for the project.
The text was updated successfully, but these errors were encountered: