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 doko
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:28:36
SpamBayes Score 8.05694e-05
Marked as misclassified No
Message-id <>
> 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.

would be very nice, but unfortunately this is not true; the multiprocessing behavior depends on configure checks testing the running kernel.
Date User Action Args
2011-08-19 21:28:37dokosetrecipients: + doko, lemburg, loewis, barry, georg.brandl, 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:28:36dokosetmessageid: <>
2011-08-19 21:28:36dokolinkissue12326 messages
2011-08-19 21:28:36dokocreate