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 sarterm
Recipients ericvw, martin.panter, sarterm
Date 2016-11-08.12:08:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1478606894.53.0.113145531974.issue28000@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry for the very late reply...

Using _LINUX_SOURCE_COMPAT is sometimes preferable, as it greatly improves compatibility with code intended for Linux and improves XPG specs compliance.

But I am not sure it should always be enabled.

In our case, we use it as there where issues with AIX malloc and hotshot when building without it, but Python seems to globally work fine without, and we did not compare performances.

Like you, I don't know why this was overridden, so it might be safer to keep the override and just add the #ifdef _LINUX_SOURCE_COMPAT.

This also applies to Python 2.7.
History
Date User Action Args
2016-11-08 12:08:14sartermsetrecipients: + sarterm, ericvw, martin.panter
2016-11-08 12:08:14sartermsetmessageid: <1478606894.53.0.113145531974.issue28000@psf.upfronthosting.co.za>
2016-11-08 12:08:14sartermlinkissue28000 messages
2016-11-08 12:08:14sartermcreate