Related setuptools change: pypa/setuptools#2896

Seems to resolve the issue. The recommended way is to set SETUPTOOLS_USE_DISTUTILS=local, apparently. Although I wonder what the gain of the change in setuptools is if everyone starts doing that…

NumPy and Scipy are looking to move to meson or cmake xref scipy/scipy#13615

NumPy and Scipy are looking to move to meson or cmake xref scipy/scipy#13615

Let's try to get Cython 3.0 released at some point, before I look into yet another build system / CI setup / wheel builder / toolchain replacement or breakage. Honestly, I've had enough of those recently.

Sure, that makes sense, and I would not expect Cython to be the first to make the jump.

Ok, your PR wins then. :-)

I will try to reproduce locally, if I can I will open an issue with setuptools.

Thanks @mattip !

Ahh, it may be a Cython thing. The ci-run.sh script is setting CC and CXX, maybe now setuptools is respecting that and not adding -pthread

Ahh, it may be a Cython thing. The ci-run.sh script is setting CC and CXX, maybe now setuptools is respecting that and not adding -pthread

cython/Tools/ci-run.sh

Lines 25 to 28 in 14ec0d1

	export CC="gcc"
	if [[ $BACKEND == *"cpp"* ]]; then
	sudo update-alternatives --set g++ /usr/bin/g++-$GCC_VERSION
	export CXX="g++"

I was always wondering why CC would be set to gcc -pthreads rather than leaving that to the application that uses it. Looks like we did similar stuff in the test setup ourselves. Oh well…

NumPy and Scipy are looking to move to meson or cmake xref scipy/scipy#13615

The proper experience for that would be greatly helped by cython learning to emit buildsystem-independent depfiles as per #1214 #1459

All the more so if cython itself wants to consider at some point switching off of setuptools :D as then it would be needed internally too.

The proper experience for that would be greatly helped by cython learning to emit buildsystem-independent depfiles as per #1214

Help with that is welcome. There was already an initial (rough) PR (#243) at some point, but I think that's only worth inspiration but not pursuing any more. cythonize collects all direct dependencies anyway in order to determine if it needs to translate a file, so writing them to disk after the fact shouldn't be difficult.