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 loewis
Recipients amaury.forgeotdarc, barry, dmalcolm, doko, eric.araujo, eric.smith, fdrake, loewis, pitrou
Date 2010-09-13.20:07:28
SpamBayes Score 1.3287112e-06
Marked as misclassified No
Message-id <4C8E847F.10509@v.loewis.de>
In-reply-to <1284391319.29.0.790745317766.issue9807@psf.upfronthosting.co.za>
Content
> My (I think fairly straightforward) idea is to just compile the
> useful values in Makefile and config.h into _sysconfig.c and arrange
> for sysconfig to import that and check it first (fallback to parsing
> mf and conf.h).

You seem to suggest that by doing so, one can actually dispose of
pyconfig.h afterwards, as all information is in the module.

This is definitely not the case: pyconfig.h continues to be required,
as an include that is literally used when compiling extension modules.
History
Date User Action Args
2010-09-13 20:07:30loewissetrecipients: + loewis, fdrake, barry, doko, amaury.forgeotdarc, pitrou, eric.smith, eric.araujo, dmalcolm
2010-09-13 20:07:28loewislinkissue9807 messages
2010-09-13 20:07:28loewiscreate