I lean towards just requiring numpy. It's super common and once a system brings in gdal python, it can't be a super constrained env where keeping things really small is critical. Just requiring numpy simplifies a number of aspects.
I think the setup.py topic as a whole is somewhat separate.l. So whichever way the numpy dep goes (required or optional), switching to pyproject.toml seems important. I'm fairly new to pyproject.toml, so I might be missing something. -Kurt On Mon, Dec 4, 2023 at 10:38 AM Even Rouault via gdal-dev < gdal-dev@lists.osgeo.org> wrote: > Hi, > > The current situation where numpy is an optional dependency of the GDAL > Python bindings is quite cumbersome to deal with our setup.py's > setuptools . All details (a bit tricky) in > https://github.com/OSGeo/gdal/issues/8069 . It seems it would be simpler > if the bindings just required numpy, which is the confugration most > people using the bindings likely actually end up using anyway. > > Any opposition to that? > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev