With a checkout of the py3k branch, building an extension module using distutils fails: error: Python.h: No such file or directory This is clearly because the wrong -I option is being supplied: gcc -pthread -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/exarkun/Projects/python-signalfd/trunk/Include -I/home/exarkun/Projects/python/branches/py3k -c signalfd/_signalfd.c -o build/temp.linux-i686-3.2/signalfd/_signalfd.o Building the extension with Python 3.1 all the way back through Python 2.3 does work, though.
Reading I'm setting this to 3.2. Given that the first alpha is due now shouldn't this be addressed, apologies if this has already happened but I don't know here to look?
Jean-Paul, can you still reproduce the bug? According to Antoine, the configure script has seen changes but sysconfig has not been updated; this could be the source of a handful of bugs.