[Python-Dev] FW: Fixing os.popen on Win32 => is the win32pipe stuff going to be adopted? (original) (raw)
M.-A. Lemburg mal@lemburg.com
Wed, 08 Mar 2000 09:46:14 +0100
- 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 win32pipe stuff going to be adopted?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Peters wrote:
Mike has a darned good point here. Anyone have a darned good answer ? -----Original Message----- From: python-list-admin@python.org [mailto:python-list-admin@python.org] On Behalf Of Mike Fletcher Sent: Tuesday, March 07, 2000 2:08 PM To: Python Listserv (E-mail) Subject: Fixing os.popen on Win32 => is the win32pipe stuff going to be adopted? Just reading one more post (and a FAQ) on the win32 pipe breakage (sewage all over the hard-disk, traffic rerouted through the bit-bucket, you aren't getting to work anytime soon Mrs. Programmer) and wondering why we have a FAQ instead of having the win32pipe stuff rolled into the os module to fix it. Is there some incompatibility? Is there a licensing problem? Ideas?
I'd suggest moving the popen from the C modules into os.py as Python API and then applying all necessary magic to either use the win32pipe implementation (if available) or the native C one from the posix module in os.py.
Unless, of course, the win32 stuff (or some of it) makes it into the core.
I'm mostly interested in this for my platform.py module... BTW, is there any interest of moving it into the core ?
-- Marc-Andre Lemburg
Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
- 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 win32pipe stuff going to be adopted?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]