4 ms·

Not the one you are asking, but NumPy literally converted to meson because of the deprecation. There was tons of pain for so many extensions. This pain generat

by tqnwx 2y ago

Not the one you are asking, but NumPy literally converted to meson because of the deprecation. There was tons of pain for so many extensions. This pain generates job security for the bigcorp employees and grief for anyone else.

itishappy 2y ago
Super helpful, thanks! The NumPy page on the migration has some details on the differences: > ... [Here] are the numpy.distutils features that are not present in setuptools: * Nested setup.py files * Fortran build support * BLAS/LAPACK library support (OpenBLAS, MKL, ATLAS, Netlib LAPACK/BLAS, BLIS, 64-bit ILP interface, etc.) * Support for a few other scientific libraries, like FFTW and UMFPACK * Better MinGW support * Per-compiler build flag customization (e.g. -O3 and SSE2 flags are default) * a simple user build config system, see site.cfg.example * SIMD intrinsics support * Support for the NumPy-specific .src templating format for .c/.h files https://numpy.org/doc/stable/reference/distutils_status_migration.html https://numpy.org/doc/stable/reference/distutils_status_migr...
- zahlman 2y ago
  I never did understand this. It appears that they were maintaining their own fork of distutils anyway (and if you open up a latest-version wheel today you should still see it included); so why did the standard library removal cause a problem?
  - handman 2y ago
    Because the "fork" still relied on the presence of the included distutils.
    - zahlman 2y ago
      But it's open source. Couldn't they just vendor it? Not like that would noticeably bloat a wheel that's already close to 20 MB on some platforms.