WinNT and python as text filter...

[Gordon McMillan]

Gaetan Corneau wrote:

[Mark Hammond, to Tim Ottinger]
> > >If so, there is a bug in the NT command prompt - you need to 
> > specify the
> > >full path to Python.exe on the command line, and it will
> > >work...
> 
> This is exactly the problem I have reported a few months ago. I
> have access to many tests machines, and two of them had this
> problem from time to time. After a reboot, it disappeared, and I
> haven't seen it again since :)

Are you sure it's the same problem?

As far as I know
 >xxx.yyy >foo.txt
does not work if xxx.yyy is executed through a file 
association. foo.txt will be created and empty. The executable 
associated to .yyy will have stdout and stderr connected to a 
bit bucket. Python doesn't have anything to do with it.

- Gordon