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 jafo
Recipients jafo, loewis, nbecker, owsla
Date 2008-01-16.07:10:51
SpamBayes Score 0.061091796
Marked as misclassified No
Message-id <1200467454.71.0.99430249334.issue1747858@psf.upfronthosting.co.za>
In-reply-to
Content
It seems like the problem here is that chown is defined to take -1 for
the arguments, where the underlying platform may define chown taking
unsigned uid/gid.

I think in the short term we will need to apply a patch like one of the
ones included here, but in the long term maybe something like
"chown(path, uid = None, gid = None)"?  With "chown(path, gid = 69)". 
Does it make sense to use None instead of -1 in the long term?
History
Date User Action Args
2008-01-16 07:30:32jafounlinkissue1747858 messages
2008-01-16 07:10:55jafosetspambayes_score: 0.0610918 -> 0.061091796
recipients: + jafo, loewis, nbecker, owsla
2008-01-16 07:10:54jafosetspambayes_score: 0.0610918 -> 0.0610918
messageid: <1200467454.71.0.99430249334.issue1747858@psf.upfronthosting.co.za>
2008-01-16 07:10:53jafolinkissue1747858 messages
2008-01-16 07:10:52jafocreate