Python 2.0 - win32pipe routines inclusion for Windows

Mark Hammond MarkH at ActiveState.com
Thu Jul 20 07:00:18 EDT 2000


"David Bolen" <db3l at fitlinxx.com> wrote in message
news:u66q3ovcg.fsf at ctwd0143.fitlinxx.com...
> I've noticed that the latest sources for Python 2.0 in CVS have
> included the win32pipe code from the PythonWin extensions as a
> replacement for the prior os.pipe() routine in Python 1.5.2.  One
> consequence of this is that you no longer receive process exit codes
> on the pipe.close() operation.  Since I need the result codes in my
> work, and work under Windows NT primarily, I figured I'd try to do
> something about it.

Great!

> wondering if this is something that should just be submitted to the
> SourceForge patch manager

Yep.

> While munging around in the source it also appears that there seems to
> be a mismatch between the ordering of file handles returned by the
> higher order popen# routines in the internal posixmodule (the
> win32pipe routines) versus the current popen2.py library module.  I
> think I saw a discussion about this in the python-dev archives, but it
> wasn't clear if the two should be consistent at this point in the
> repository.

Although I recall the discussion, I can't recall the outcome.  Add this
comment to the patch (but not, at this stage, the code to correct it)

Mark.






More information about the Python-list mailing list