[issue29605] platform.architecture() with Python2.7-32 misreports architecture on macOS.

2017-02-20 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: Ok, thanks for the clarification. So if I understand correctly, the main change in Python 3 is that points to the stub launcher, not the binary itself. In any case, a new function would have to be added to the platform module to query multiple

[issue29605] platform.architecture() with Python2.7-32 misreports architecture on macOS.

2017-02-20 Thread Ned Deily
Ned Deily added the comment: > AFAIK, the Python 3 binaries available from python.org are no longer built as > universal binaries, so the problem doesn't show with those. All python.org Mac binaries are built as universal. For example: $ file /usr/local/bin/python3.6 /usr/local/bin/python3.6:

[issue29605] platform.architecture() with Python2.7-32 misreports architecture on macOS.

2017-02-20 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: Thanks for the report, but there really isn't much we can do, since the API is not geared up for handling executables which contain binaries for multiple architectures. AFAIK, the Python 3 binaries available from python.org are no longer built as

[issue29605] platform.architecture() with Python2.7-32 misreports architecture on macOS.

2017-02-20 Thread Ned Deily
Ned Deily added the comment: platform.architecture() is documented as giving unreliable results with macOS universal files; see https://docs.python.org/2/library/platform.html#platform.architecture. The difference in behavior between Python 2.7 and 3.x for the example you show is due to the