I rebased my PR and squashed all commits into a single commit. The test should now pass on Windows, Linux and macOS ;-)

@malemburg, @ned-deily, @ronaldoussoren: So, what do you think of:

$ python3.8 -m platform
macOS-10.13.6-x86_64-i386-64bit

instead of:

$ python3.8 -m platform
Darwin-17.7.0-x86_64-i386-64bit

?

Is there any reason to not change platform.platform() in Python 3.8 on macOS?

@malemburg, @ned-deily, @ronaldoussoren: So, what do you think of:

$ python3.8 -m platform
macOS-10.13.6-x86_64-i386-64bit

instead of:

$ python3.8 -m platform
Darwin-17.7.0-x86_64-i386-64bit

?

I like this, information about macOS is more interesting than information about the kernel version.

I'm not very happy with the processor information at the end, but that's unrelated to the change you are proposing:

1. I don't understand why both 'uname -m' and 'uname -p' are present in this string. Does that ever add useful information?

2. The information does not include data about fat binaries, resulting amongst others in the following inconsistency:

ronald@Menegroth[0]$ arch -i386 python3.6 -m platform
Darwin-18.2.0-x86_64-i386-64bit

ronald@Menegroth[0]$ arch -i386 python3.6 -c 'import sys; print(sys.maxsize)'
2147483647

This platform output includes "64bit" because the binary for python3.6 includes support for both i386 and x86_64, and doesn't show that the command is using i386 instructions.

This platform output includes "64bit" because the binary for python3.6 includes support for both i386 and x86_64, and doesn't show that the command is using i386 instructions.

To be honest, I don't understand the purpose of the platform.architecture() function :-) For me, sys.maxsize > 2**31 should be enough to distinguish 32 and 64 bits platforms, no?

Ronald:

This is something for another pull request, but the 'MacOS' bits you mention here are a leftover from the long removed MacOS 9 port and should be removed.

I wrote PR #10959 for that.

I'm not very happy with the processor information at the end, but that's unrelated to the change you are proposing: (...)

@ronaldoussoren: Please open a new issue if you would like to change that. I have no idea why we have the current info nor how to change them.