da-woods schrieb am 13.02.25 um 09:16: > Most people will probably want to do this from setup.py instead of > calling an executable [...]
we need something that can be run from the command-line, but the main users are build systems (e.g. scikit-build/ meson) and not people.
What I understood from past discussions was that build systems (specifically Meson) would rather prefer calling "cython" over a "setup.py" build. Especially for larger packages like SciPy. Thus my comments regarding the "cython" CLI interface.
Programmatic "setup.py" / setuptools builds are more and more replaced by declarative build setups in the Python world. I'm therefore not sure how important "setup.py" support for this (new) feature still is. My gut feeling is that it's still relevant because C/C++ module builds tend to be non-trivial (and thus benefit from programmatic freedom), at least as soon as external native libraries are involved.
Still, support in "cythonize()" seems most natural to me, given the interface of "here's a bunch of source files, now set up the extension module configuration for me". A shared library seems to fit perfectly into that approach, yielding an additional Extension config for the shared module and adapting the config of dependent modules to use it.
Stefan _______________________________________________ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
