RetroSearch Browse

Fri Mar 23 17:30:37 CET 2007 · http://mail.python.org/pipermail/python-dev/2007-March/072309.html

On 3/23/07, Hrvoje Nikšić <hrvoje.niksic at avl.com> wrote:
> On Thu, 2007-03-22 at 13:38 -0700, Guido van Rossum wrote:
> > Sounds good to me. In 3.0 we should probably not have os.popen*(), nor
> > the popen2 module at all, and do everything via the subprocess module.
> > I wonder if we should even get rid of os.system(); then there should
> > be a subprocess.system() instead. And do we even need os.fork(),
> > os.exec*(), os.spawn*()?
>
> Please don't remove os.fork and os.exec*.  Some people need to fine-tune
> process creation and don't need portability to non-Unix OS'es.  For
> them, the functions that call the underlying system API and little or
> nothing else are a god-send.

Right, but if you're really using only Posix, you can simply use
``posix.fork`` and ``posix.exec*`` and then you're even being explicit
about the fact.

STeVe
-- 
I'm not *in*-sane. Indeed, I am so far *out* of sane that you appear a
tiny blip on the distant coast of sanity.
        --- Bucky Katt, Get Fuzzy

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2007-March/072309.html below:

[Python-Dev] deprecate commands.getstatus()