[issue8747] Autoconf tests in python not portably correct

Enji Cooper added the comment: This issue has been superseded by other work. -- stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue8747] Autoconf tests in python not portably correct

Mark Lawrence added the comment: >From msg112274 "if these platforms can't function with these preprocessor >defines, the platforms need to be fixed -- not python." so I believe this can >be closed. -- nosy: +BreamoreBoy ___ Python tracker

[issue8747] Autoconf tests in python not portably correct

Garrett Cooper added the comment: The issue is still present. The overall problem I suppose is with consistency and presentation of features in the python language. Many features cannot be presented in a 100% portable manner, and the problem is that such features that aren't POSIX conforming

[issue8747] Autoconf tests in python not portably correct

Éric Araujo added the comment: doko, I made you nosy because of your autotools expertise. Hope it’s okay. -- ___ Python tracker ___ __

[issue8747] Autoconf tests in python not portably correct

Éric Araujo added the comment: Garrett, does the bug still exist in 3.2 (branch named py3k in subversion)? -- nosy: +doko, merwok versions: +Python 3.2 -Python 2.6 ___ Python tracker ___

[issue8747] Autoconf tests in python not portably correct

New submission from Garrett Cooper : A number of features are being blindly enabled on python that aren't correct from a porting standpoint; a handful in configure.in I noticed are: # The later defininition of _XOPEN_SOURCE disables certain features # on Linux, so we need _GNU_SOURCE to re-enab