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 martin.panter
Recipients Arfrever, doko, eric.snow, gregory.p.smith, koobs, loewis, martin.panter, ned.deily, petri.lehtinen, pitrou, python-dev, rpetrov, sbt, trent, vstinner, zach.ware
Date 2016-09-12.01:49:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I’m not sure what the overall status of this bug is, so I will leave the versions as they are. Are the three comments from 2013 relevant, and is there anything I can do to help?

The Python 2 code already unconditionally adds -IInclude (see Issue 786737), and does not use BASECPPFLAGS. I think it would better to remove Trent’s code, as in unused-flags.patch.

Python 3 also has this unconditional -IInclude, so maybe we can eliminate one of them in Python 3?

gcc -pthread -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes    -Werror=declaration-after-statement  -IObjects -IInclude -IPython -I. -IInclude -I../Include    -DPy_BUILD_CORE -o Python/Python-ast.o Python/Python-ast.c
Date User Action Args
2016-09-12 01:49:51martin.pantersetrecipients: + martin.panter, loewis, doko, gregory.p.smith, pitrou, vstinner, ned.deily, trent, rpetrov, Arfrever, python-dev, sbt, eric.snow, petri.lehtinen, zach.ware, koobs
2016-09-12 01:49:51martin.pantersetmessageid: <>
2016-09-12 01:49:51martin.panterlinkissue15819 messages
2016-09-12 01:49:50martin.pantercreate