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, Ramchandra Apte, amaury.forgeotdarc, barry, benjamin.peterson, djc, dmalcolm, doko, eric.araujo, ezio.melotti, foom, gagern, georg.brandl, jwilk, lemburg, loewis, petri.lehtinen, pitrou, python-dev, r.david.murray, rosslagerwall, sandro.tosi, vstinner
Date 2011-08-19.21:16:21
SpamBayes Score 2.99533e-09
Marked as misclassified No
Message-id <4E4ED2A4.1040409@v.loewis.de>
In-reply-to <4E4EC420.8060207@egenix.com>
Content
>> The only way I can read this argument that makes any sense to me is
>> that you are arguing for a precise build-time OS string.  If it is
>> supposed to be an argument in favor of keeping 'linux3' it makes no
>> sense, since '2' vs '3' is in no way a useful line of demarcation
>> when it comes to linux.

The build time Linux kernel has no effect on Python's build procedure
whatsoever. Python does not use the kernel at all for building; it
only uses the C library headers, and the kernel headers that happen
to be incorporated into the version of the C library installed. That
affects what features get selected during build time.

Notice that the proposed fix to keep os.platform to "linux2" actually
means that there is *no change*, as os.platform always was "linux2"
on the system. It is a bug that it reports "linux3" in some cases,
and that bug is being fixed.
History
Date User Action Args
2011-08-19 21:16:22loewissetrecipients: + loewis, lemburg, barry, georg.brandl, doko, amaury.forgeotdarc, gagern, foom, pitrou, vstinner, benjamin.peterson, jwilk, djc, ezio.melotti, eric.araujo, Arfrever, r.david.murray, dmalcolm, sandro.tosi, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-08-19 21:16:21loewislinkissue12326 messages
2011-08-19 21:16:21loewiscreate