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 jaraco, lemburg, pitrou
Date 2019-03-08.16:34:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <62a94ce3-8aa4-5c56-d6ad-e2641d90433d@egenix.com>
In-reply-to <1552061552.75.0.667583853795.issue35967@roundup.psfhosted.org>
Content
Jason: StackExchange does have lots of good hints, but it's not always
the correct. In this case, it's clearly wrong. uname -p has been
available on many Unix installations for decades.

I started writing the module back in 1999 and even then, the support
was already working on the systems I used at the time, and several
others, as you can see from this page:

https://www.egenix.com/www2002/python/mxCGIPython.html

The module was originally created to come up with a good name to
use for identifying platform binaries coming out of my mxCGIPython
project.

Note that the processor is not always needed to determine whether
software runs on a machine or not. The "uname -m" output often
is enough, but there are cases where e.g. compiler options are
used which produces code that only works on particular processors.

Perhaps adding a more capable API to interface to /proc/cpuinfo
would be a good idea.
History
Date User Action Args
2019-03-08 16:34:32lemburgsetrecipients: + lemburg, jaraco, pitrou
2019-03-08 16:34:32lemburglinkissue35967 messages
2019-03-08 16:34:32lemburgcreate