Author exarkun
Recipients amaury.forgeotdarc, asksol, elprans, exarkun, flub, giampaolo.rodola, loewis, marcelo_fernandez
Date 2009-09-16.15:35:11
SpamBayes Score 8.45685e-10
Marked as misclassified No
Message-id <1253115314.35.0.638299668716.issue5672@psf.upfronthosting.co.za>
In-reply-to
Content
> prctl is not portable. I always thought that the premise of stdlib is to
> provide portable interfaces.  BSD, for example, uses setprocname instead
> of prctl.  Also, prctl does not modify the process name shown in "ps
> uxww". Here's how PostgreSQL does this: http://tinyurl.com/mhjuqc.

Many parts of the stdlib are not portable.  It is perfectly appropriate
for the stdlib to expose a low-level, platform-specific API directly and
in a way which makes the Python API similarly low-level and non-portable.

That's not to say that a cross-platform API cannot *also* be provided,
though, assuming the functionality can be implemented *somehow* on other
platforms.  So I agree with Martin.  prctl should be exposed as-is.  If
someone would also like to expose similar functionality on on other
platforms, great.  And if someone would like to provide a cross-platform
API based on these, also great.
History
Date User Action Args
2009-09-16 15:35:14exarkunsetrecipients: + exarkun, loewis, amaury.forgeotdarc, giampaolo.rodola, flub, marcelo_fernandez, elprans, asksol
2009-09-16 15:35:14exarkunsetmessageid: <1253115314.35.0.638299668716.issue5672@psf.upfronthosting.co.za>
2009-09-16 15:35:12exarkunlinkissue5672 messages
2009-09-16 15:35:11exarkuncreate