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 Michael.Felt
Recipients Arfrever, Dima.Tisnek, Michael.Felt, djones, eric.araujo, jaraco, jkloth, madprog, ned.deily, pitrou, sferencik, tarek
Date 2016-10-31.20:34:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
FYI: This is 'actual' as I am working on an implementation of a cloud-init distro for AIX and it is very difficult to figure out the correct approach for a replacement value for os.uname[4] - when comparing with "Linux" logic

I was thinking of using


but both are 32-bit on 64-bit hardware:

>>> platform.platform().split("-")
['AIX', '1', '00C291F54C00', 'powerpc', '32bit']
>>> platform.platform().split("-")[4]
>>> platform.platform().split("-")[3]

>>> platform.platform().split("-")
['Linux', '3.2.0', '4', 'powerpc64', 'ppc64', 'with', 'debian', '7.8']
>>> platform.platform().split("-")[4]
>>> platform.platform().split("-")[3]

This - also - seems tricky re: the placement of the -
>>> platform.platform()

compared with:
>>> platform.platform()

Truely, some guidance from "the powers that be" is needed if there is ever to be uniformity. And if it 'cannot' be patched on 'old' versions, at least there will be a way to hack clarity into code (imho, a patch is better rather than hacks creating continued diversity - everyone continues to use their understanding of intent, creating new diverse wishes (aka features not benefits)) for what the code "must" do - because there are so many projects that used it this way (and others that used it that way) ....

Date User Action Args
2016-10-31 20:34:26Michael.Feltsetrecipients: + Michael.Felt, jaraco, pitrou, tarek, jkloth, ned.deily, eric.araujo, Arfrever, madprog, Dima.Tisnek, sferencik, djones
2016-10-31 20:34:26Michael.Feltsetmessageid: <>
2016-10-31 20:34:26Michael.Feltlinkissue18987 messages
2016-10-31 20:34:26Michael.Feltcreate