subprocess pipe fails under Emacs

[andersjm]

BPO	1163759

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2005-03-19.07:07:59.000>
created_at = <Date 2005-03-15.14:49:55.000>
labels = ['library']
title = 'subprocess pipe fails under Emacs'
updated_at = <Date 2005-03-19.07:07:59.000>
user = 'https://bugs.python.org/andersjm'

bugs.python.org fields:

activity = <Date 2005-03-19.07:07:59.000>
actor = 'astrand'
assignee = 'astrand'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2005-03-15.14:49:55.000>
creator = 'andersjm'
dependencies = []
files = []
hgrepos = []
issue_num = 1163759
keywords = []
message_count = 2.0
messages = ['24649', '24650']
nosy_count = 2.0
nosy_names = ['astrand', 'andersjm']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1163759'
versions = []

[andersjm]

Creating a pipe with subprocess.Popen fails if Python
is running in a non-interactive subshell under XEmacs
on MSWin.

This program
import subprocess
pipe = subprocess.Popen(['cmd', '/c', r'echo', 'Hi
there!'],
stdout=subprocess.PIPE)
print pipe.stdout.read()

produces the expected "Hi there!" when run from a
console. But when run from an XEmacs non-interactive
subshell, I get this traceback:

Traceback (most recent call last):
  File "C:\temp\subprocessbug.py", line 3, in ?
    stdout=subprocess.PIPE)
  File "c:\App\Dev\Python24\lib\subprocess.py", line
545, in __init__
    (p2cread, p2cwrite,
  File "c:\App\Dev\Python24\lib\subprocess.py", line
605, in _get_handles
    p2cread = self._make_inheritable(p2cread)
  File "c:\App\Dev\Python24\lib\subprocess.py", line
646, in _make_inheritable
    DUPLICATE_SAME_ACCESS)
TypeError: an integer is required

Python 2.4 (#60, Nov 30 2004, 11:49:19) [MSC v.1310 32
bit (Intel)]
W2K, XEmacs 21.4p13

[astrand]

Logged In: YES
user_id=344921

This problem has been reported on bug 1126208.