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 loewis
Recipients amaury.forgeotdarc, loewis, solinym
Date 2009-08-22.07:48:50
SpamBayes Score 7.2132594e-10
Marked as misclassified No
Message-id <>
In-reply-to <>
> Where would be the best place to put these non-POSIX calls?
> I looked at posixmodule.c and it's a mess; much conditional CPP logic
> governing what gets compiled, not clear where I should add something
> like this there - if I should at all, since these routines are not POSIX
> routines.

Don't worry about that - the POSIX module is the right place, despite
it's name.

> Perhaps there should be a module called Unix or something?

That wouldn't reduce the need to remove CPP logic. I personally don't
find that CPP logic very messy - most of it is fairly clear (perhaps
with popen being the exception).

> Also, knowing whether the functions were avaiable at compile time would
> be tricky; some Unix OSes have them and others don't.

I don't understand. When you compile for a specific Unix, it either has
them or not, right? So you *can* test at compile time, and easily so
(the same way it test for about 20 other functions).

> It sounds like a
> job for autoconf to define HAVE_SETRESUID and other CPP definitions like
> that so we can compile cleanly and portably...

Correct - you need to change as well.
Date User Action Args
2009-08-22 07:48:52loewissetrecipients: + loewis, amaury.forgeotdarc, solinym
2009-08-22 07:48:50loewislinkissue6508 messages
2009-08-22 07:48:50loewiscreate