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 Alexander.Belopolsky
Recipients Alexander.Belopolsky, l0nwlf, loewis, orsenthil, r.david.murray, ronaldoussoren
Date 2010-02-24.18:02:50
SpamBayes Score 1.7541524e-14
Marked as misclassified No
Message-id <d38f5331002241002y7280fd70o90970eede81e0d2c@mail.gmail.com>
In-reply-to <1267033501.34.0.255220137437.issue7900@psf.upfronthosting.co.za>
Content
On Wed, Feb 24, 2010 at 12:45 PM, Martin v. Löwis
<report@bugs.python.org> wrote:
..
> I still think that the sysconf version should be the correct one. If OSX fails to work correctly under
> that version, and causes Python to raise an exception - then that's a platform bug, and should only > accept minimal work arounds.
>

It is more than an exception.  In python 2.6+, os.getgroups() returns
wrong results.  It always reads system database instead of returning
the values that are set with os.setgroups().

> So I propose to close this as "won't fix". Or, the original issue could be resolved by accepting
> EINVAL on OSX as a correct result of getgroups in the test suite.
>

Supporting more than 16 groups is less important (and impossible
without a platform fix) than to have working get/setgroups for
reasonable number of groups.  This is how python behaved before
r63955.

At the very least unit tests that I submitted could be accepted
possibly with a skip on OSX if fixing the bug is not an option.
History
Date User Action Args
2010-02-24 18:02:52Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, loewis, ronaldoussoren, orsenthil, r.david.murray, l0nwlf
2010-02-24 18:02:50Alexander.Belopolskylinkissue7900 messages
2010-02-24 18:02:50Alexander.Belopolskycreate