Message 59995 - Python tracker

➜

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	owsla
Recipients	jafo, loewis, nbecker, owsla
Date	2008-01-16.12:55:27
SpamBayes Score	0.00422308
Marked as misclassified	No
Message-id	<1200488215.71.0.651619236187.issue1747858@psf.upfronthosting.co.za>
In-reply-to

Content
The idea of dynamic typing it seems quite heavy to me, but I'm not a Python hacker, so I don't know what's the norm. Notice that os.stat() does "PyInt_FromLong((long)st->st_uid)" on the stat structure's st_uid field. On my platform (OS X 10.4), st_uid is defined as a uid_t type. So maybe os.stat() has the answer: ignore the signed vs. unsigned int problem and just use a long. The actual chown() call in posix_chown() casts the uid variable to a (uid_t) anyway. GCC doesn't seem to complain when we cast a long to an unsigned int, even.

The idea of dynamic typing it seems quite heavy to me, but I'm not a
Python hacker, so I don't know what's the norm.

Notice that os.stat() does "PyInt_FromLong((long)st->st_uid)" on the
stat structure's st_uid field. On my platform (OS X 10.4), st_uid is
defined as a uid_t type.

So maybe os.stat() has the answer: ignore the signed vs. unsigned int
problem and just use a long. The actual chown() call in posix_chown()
casts the uid variable to a (uid_t) anyway. GCC doesn't seem to complain
when we cast a long to an unsigned int, even.

History
Date	User	Action	Args
2008-01-16 12:56:55	owsla	set	spambayes_score: 0.00422308 -> 0.00422308 recipients: + owsla, loewis, jafo, nbecker
2008-01-16 12:56:55	owsla	set	spambayes_score: 0.00422308 -> 0.00422308 messageid: <1200488215.71.0.651619236187.issue1747858@psf.upfronthosting.co.za>
2008-01-16 12:55:27	owsla	link	issue1747858 messages
2008-01-16 12:55:27	owsla	create