[issue4591] uid/gid problem in os.chown

2008-12-09 Thread Sjoerd Mullender
Sjoerd Mullender [EMAIL PROTECTED] added the comment: I'm sure you meant 2^32-2 ;-). The fix to use long doesn't seem right to me either. unsigned int is a better match with uid_t and gid_t. ___ Python tracker [EMAIL PROTECTED]

[issue4591] uid/gid problem in os.chown

2008-12-08 Thread Sjoerd Mullender
New submission from Sjoerd Mullender [EMAIL PROTECTED]: On Fedora 8 and 10 using Python 2.5.1 and 2.5.2 (64 bit): $ grep nfsnobody /etc/passwd nfsnobody:x:4294967294:4294967294:Anonymous NFS User:/var/lib/nfs:/sbin/nologin So the UID of nfsnobody is 4294967294 (-2 if viewed as signed 32-bit

[issue4591] uid/gid problem in os.chown

2008-12-08 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: This was already corrected by r61540, and will be released with 2.5.3 and 2.6.2. BUT -- fchown() was not modified. patch is similar to r61540, but I don't know how to test: Index: posixmodule.c

[issue4591] uid/gid problem in os.chown

2008-12-08 Thread STINNER Victor
STINNER Victor [EMAIL PROTECTED] added the comment: 2^31-2 doesn't fit in long on 32 bits CPU. On my Linux box, uid_t is an unsigned integer (32 bits unsigned integer). Why not using unsigned int? chown prototype: int chown(const char *path, uid_t owner, gid_t group); -- nosy: