Windows STDIN/STDOUT Redirection is actually FIXED

[NacsaKristf]

BPO	15962
Nosy	@terryjreedy, @tjguk
Files	15962.patch

^{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 2014-07-13.18:35:46.676>
created_at = <Date 2012-09-18.12:19:54.216>
labels = ['easy', 'type-feature', 'expert-installation', 'OS-windows', 'docs']
title = 'Windows STDIN/STDOUT Redirection is actually FIXED'
updated_at = <Date 2014-07-13.18:35:46.675>
user = 'https://bugs.python.org/NacsaKristf'

bugs.python.org fields:

activity = <Date 2014-07-13.18:35:46.675>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = True
closed_date = <Date 2014-07-13.18:35:46.676>
closer = 'terry.reedy'
components = ['Documentation', 'Installation', 'Windows']
creation = <Date 2012-09-18.12:19:54.216>
creator = 'Nacsa.Krist\xc3\xb3f'
dependencies = []
files = ['27839']
hgrepos = []
issue_num = 15962
keywords = ['patch', 'easy']
message_count = 4.0
messages = ['170641', '174499', '177575', '222920']
nosy_count = 6.0
nosy_names = ['terry.reedy', 'tim.golden', 'docs@python', 'BreamoreBoy', 'Nacsa.Krist\xc3\xb3f', 'dhgmgn']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue15962'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3', 'Python 3.4']

[NacsaKristf]

The Python docs faq says that due to a bug in Windows NT's cmd.exe, the output redirection and piping won't work when started from file extension.

http://docs.python.org/faq/windows.html#how-do-i-make-python-scripts-executable
http://docs.python.org/py3k/faq/windows.html#how-do-i-make-python-scripts-executable

This is actually fixed in Windows, but the fix is disabled by default, and you need to enable it in regedit, the keyword is "InheritConsoleHandles".

Proof & Details:
http://support.microsoft.com/default.aspx?kbid=321788

It would be great if the docs could refer to this fix, as the docs is the major source of information for many.

[dhgmgn]

I've referenced the kb article in the docs. Please let me know if the fix is ok - maybe the whole registry change process should be included in the docs directly?

[NacsaKristf]

@dhgmgn I think the change is ok. That said, I add two things.

It maybe should be noted which Windows version has this corrected.
The article contains this string: "This problem was first corrected in Microsoft Windows 2000 Service Pack 4. This problem was first corrected in Windows XP Service Pack 1".

The other thing is that I prefer if the relevant information is copied due to various reasons. One reason is that it serves as a "highlight" (nice time-saver and is also against TL;DR situations). Another is that Microsoft may simply cease support, or discontinue this link (they tend to do this).

I'm not familiar with how the python docs is constructed, if there is a style guide, etc., but I can tell that I'd be happy if I could see this information there directly. This is also how I've found out about that cmd header line/'trick'.

@<everyone>
Another thing, can anyone else confirm that this works for [s]he?
I've tested this on an 32-bit xp pro sp3.

When not using the fix, something like foo | myscript.py | bar results in:
IOError: [Errno 9] Bad file descriptor
With using the registry fix from Microsoft, the command from above just works for me on the XP. (The cmd.exe/console needs to be restarted.)

[BreamoreBoy]

This can be closed as "out of date" as extensive changes made to the Windows FAQ have removed the wording referenced in the patch.