➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jonathan.Wakely
Recipients Jonathan.Wakely, eugene_beast, loewis
Date 2013-05-10.15:37:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368200246.24.0.651875616034.issue1045893@psf.upfronthosting.co.za>
In-reply-to
Content 
Insisting on including Python.h first is just broken.

GNU libc's /usr/include/features.h will override it anyway when _GNU_SOURCE is defined:

# undef  _POSIX_C_SOURCE
# define _POSIX_C_SOURCE    200809L
# undef  _XOPEN_SOURCE
# define _XOPEN_SOURCE  700

So if you define _GNU_SOURCE ( which happens automatically when using G++) the annoying defines in pyconfig.h are overridden anyway, so why not just only define them if not already defined?

Either you include Python.h first and its settings get ignored by glibc, or you don't include it first and you get annoying warnings.
History
Date User Action Args
2013-05-10 15:37:26Jonathan.Wakelysetrecipients: + Jonathan.Wakely, loewis, eugene_beast
2013-05-10 15:37:26Jonathan.Wakelysetmessageid: <1368200246.24.0.651875616034.issue1045893@psf.upfronthosting.co.za>
2013-05-10 15:37:26Jonathan.Wakelylinkissue1045893 messages
2013-05-10 15:37:26Jonathan.Wakelycreate