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 belopolsky
Recipients belopolsky, flox, l0nwlf, loewis, michael.foord, orsenthil, r.david.murray, ronaldoussoren
Date 2010-07-08.21:18:13
SpamBayes Score 0.0002939535
Marked as misclassified No
Message-id <AANLkTikRebI7DqItkJIr3DNtGQb91g01e7ZBHNJAFhI7@mail.gmail.com>
In-reply-to <1278622333.99.0.917083890955.issue7900@psf.upfronthosting.co.za>
Content
This whole thing is a mess.  Great analysis, by the way.   I started a
similar experiment some time ago, but gave up when I discovered that a
member of the admin group can read any file regardless of permissions
settings.  Your solution is probably the best we can do for 2.7, but
for 3.x I still believe it is better to add os.getgrouplist and
document that on OSX users should use it in preference of
os.getgroups.  (A better explanation of the difference between the two
will probably be even better.)

On Thu, Jul 8, 2010 at 4:52 PM, Ronald Oussoren <report@bugs.python.org> wrote:
..
> The behaviour w.r.t. secondairy groups is rather different than what I'd expect on a Unix system.
History
Date User Action Args
2010-07-08 21:18:16belopolskysetrecipients: + belopolsky, loewis, ronaldoussoren, orsenthil, r.david.murray, michael.foord, flox, l0nwlf
2010-07-08 21:18:14belopolskylinkissue7900 messages
2010-07-08 21:18:13belopolskycreate