os.uname() on Darwin space in machine

[timcarlson]

BPO	560311
Nosy	@loewis, @jackjansen

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/jackjansen'
closed_at = <Date 2002-07-08.13:52:07.000>
created_at = <Date 2002-05-24.20:50:04.000>
labels = ['invalid', 'library']
title = 'os.uname() on Darwin space in machine'
updated_at = <Date 2002-07-08.13:52:07.000>
user = 'https://bugs.python.org/timcarlson'

bugs.python.org fields:

activity = <Date 2002-07-08.13:52:07.000>
actor = 'jackjansen'
assignee = 'jackjansen'
closed = True
closed_date = None
closer = None
components = ['Distutils']
creation = <Date 2002-05-24.20:50:04.000>
creator = 'timcarlson'
dependencies = []
files = []
hgrepos = []
issue_num = 560311
keywords = ['patch']
message_count = 3.0
messages = ['40120', '40121', '40122']
nosy_count = 3.0
nosy_names = ['loewis', 'jackjansen', 'timcarlson']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue560311'
versions = ['Python 2.2']

[timcarlson]

os.uname() on Darwin (Mac OS X) returns a string for
"machine" of
"Power MacIntosh" which can cause problems. Getting rid
of the space might be a good thing

[loewis]

Logged In: YES
user_id=21627

There's no uploaded file! You have to check the
checkbox labeled "Check to Upload & Attach File"
when you upload a file.

Please try again.

(This is a SourceForge annoyance that we can do
nothing about. :-( )

[jackjansen]

Logged In: YES
user_id=45365

os.uname() is simply a wrapper around the C library function of te same name. It returns "Power Macintosh" as the machine type.

For reasons I don't understand the C interface doesn't allow you to get at the "generic processor type" that is returned by "uname -p". This would probably be more useful (as the value is "powerpc"). But then, Linux gets it wrong, and returns "i686" for machine name and "unknown" for processor type, exactly the wrong way around.