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 Arfrever, eric.araujo, lemburg, loewis, vstinner
Date 2011-08-22.09:24:44
SpamBayes Score 1.10288e-05
Marked as misclassified No
Message-id <>
In-reply-to <>
> Well, it is important to somehow get the build information for
> Python, since that tells us which OS features were available
> at the time of compilation.

No, it doesn't (except for a bug that Matthias Klose pointed out).
The OS kernel version should have *zero* impact on the resulting Python
binary. What matters it the C compiler and the version of the C library.
The C library may or may not have features; features of the kernel used
to build Python are completely irrelevant.

(I think you misunderstood an earlier statement of me as
self-contradicting. It was not: The kernel *headers* may have an
impact during autoconf, not the running kernel. For Linux, the
kernel headers are part of the C library, and typically bear no
relationship with the running kernel - i.e. they may be either older
or newer than the running kernel).

Since there is no chance that we get the build environment captured
in a reasonable way (in particular not the version of the C library,
in a cross-platform manner), I strongly recommend to let this aspect
Date User Action Args
2011-08-22 09:24:45loewissetrecipients: + loewis, lemburg, vstinner, eric.araujo, Arfrever
2011-08-22 09:24:44loewislinkissue12794 messages
2011-08-22 09:24:44loewiscreate