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

Showing content from https://mail.python.org/pipermail/python-dev/2000-March/002542.html below:

Fixing os.popen on Win32 => is the win32pipe stuff going to be adopted?

• Previous message: [Python-Dev] FW: Fixing os.popen on Win32 => is the win32pipe stuff going to be adopted?
• Next message: [Python-Dev] FW: Fixing os.popen on Win32 => is the win32pipestuff going to be adopted?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 9 Mar 2000, James C. Ahlstrom wrote:
>...
> > libc pipes ares as flaky as libc popen under Windows, Jim!  MarkH has the
> > only versions of these things that come close to working under Windows (he
> > wraps the native Win32 spellings of these things; MS's libc entry points
> > (which Python uses now) are much worse).
> 
> I believe you when you say popen() is flakey.  It is a little
> harder to believe it is not possible to write a _popen()
> replacement using pipes which works.
> 
> Of course I wanted you to do it instead of me!  Well, if
> I get any time before 1.6 comes out...

It *has* been done. Bill Tutt did it a long time ago. That's what
win32pipe is all about.

-g

-- 
Greg Stein, http://www.lyra.org/

• Previous message: [Python-Dev] FW: Fixing os.popen on Win32 => is the win32pipe stuff going to be adopted?
• Next message: [Python-Dev] FW: Fixing os.popen on Win32 => is the win32pipestuff going to be adopted?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4