[issue9053] distutils compiles extensions so that Python.h cannot be found

Changes by Éric Araujo : -- stage: -> committed/rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue9053] distutils compiles extensions so that Python.h cannot be found

Changes by Jean-Paul Calderone : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue9053] distutils compiles extensions so that Python.h cannot be found

Jean-Paul Calderone added the comment: exar...@boson:~/Projects/python-signalfd/trunk$ PYTHONPATH= ~/Projects/python/branches/py3k/python setup.py build_ext -i running build_ext building 'signalfd._signalfd' extension creating build creating build/temp.linux-i686-3.2 creating build/temp.linux-i

[issue9053] distutils compiles extensions so that Python.h cannot be found

Éric Araujo added the comment: 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. -- nosy: +eric.araujo ___ Pyth

[issue9053] distutils compiles extensions so that Python.h cannot be found

Mark Lawrence added the comment: Reading msg108321 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? -- nosy: +BreamoreBoy versions: +Python 3.2 -Python 3.1 __

[issue9053] distutils compiles extensions so that Python.h cannot be found

New submission from Jean-Paul Calderone : 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 -Ws