Message116346
| 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. |
|