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 lemburg
Recipients Arfrever, ezio.melotti, lemburg, loewis, nadeem.vawda, vstinner
Date 2011-08-22.14:26:22
SpamBayes Score 1.28364e-11
Marked as misclassified No
Message-id <>
In-reply-to <>
STINNER Victor wrote:
> STINNER Victor <> added the comment:
>> sys.platform refers to build time information,
>> so the platform module won't help.
> When I wrote my patch, I realized that sys.platform is used to get the runtime information, which is wrong. See the tests in Lib/test/test_*.py: they use sys.platform to check features of the running OS (kernel). It is mostly to test FreeBSD major version, and it looks like Python is build on the same FreeBSD major version that it is running on. Maybe because on FreeBSD, most programs are compiled instead of using prebuild packages (pkgadd).

Right. FreeBSD doesn't ship prebuilt binaries for packages -
it uses a very elegant "ports" collection, where everything gets
compiled on the target machine:

So you don't really run into the issue of using a older Python build
on the system, unless you have an application which ships Python
along with the application package.
Date User Action Args
2011-08-22 14:26:23lemburgsetrecipients: + lemburg, loewis, vstinner, nadeem.vawda, ezio.melotti, Arfrever
2011-08-22 14:26:22lemburglinkissue12795 messages
2011-08-22 14:26:22lemburgcreate