On approximately 10/31/2008 5:06 AM, came the following characters from
the keyboard of Bill McClain:
On 2008-10-31, Glenn Linderman <[EMAIL PROTECTED]> wrote:
The problem with stdin/stdout is on Windows 2000 (and maybe the earlier
NT?). But not on XP or AFAIK Vista.
It only occurs when a program is executed indirectly using the file
associations instead of directly via the command line.
File associations, are the Windows "let's do it a different way"
alternative for Unix she-bang lines (#!/path/to/python).
Can you elaborate on this?
What I reported is what I remembered from when XP came out. Seems like
Testing now indicates that it doesn't work so well on XP at this point.
That either means that my memory was faulty, or that some XP update
broke it again.
What I remember for sure, is that this is not a new problem; that it was
introduced in some version of Windows, that it was fixed in some later
version of Windows. The whole issue totally predates Vista, so it would
have had to have been the introduction of 2000 or XP that fixed it. Or
a service pack.
Here is what Google helped me find that M$ remembers:
http://support.microsoft.com/kb/321788 (Ah, I see Tim found this too)
Looks like it was broken in both 2000 and XP, and fix in both via a
service pack or hot fix, but seems to now be broken again?
Creating the registry setting mentioned in this kb article didn't
(immediately) solve the problem. Next time I reboot, I'll try to
remember to test this again.
--
Glenn -- http://nevcal.com/
===========================
A protocol is complete when there is nothing left to remove.
-- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
--
http://mail.python.org/mailman/listinfo/python-list
