Marc-Andre Lemburg <m...@egenix.com> added the comment:
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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35967> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
