Re: Invoking Python from Cygwin problem.

2006-11-25 Thread Ant
Cousin Stanley wrote: ... > Using Cygwin and Python 2.4 under Win2K the following version > of your code seems to work OK here with no extraneous CR Hmm. Just tried it here at home (Python 2.5) and it works fine as well... Cygwin was pre-installed on my machine when I started work at the

Re: Invoking Python from Cygwin problem.

2006-11-25 Thread Cousin Stanley
> Hi all, > > Using cygwin and Python 2.5, I have the following scripts, > one bash script and the other a python script: > -- Ant Using Cygwin and Python 2.4 under Win2K the following version of your code seems to work OK

Re: Invoking Python from Cygwin problem.

2006-11-25 Thread Ant
Marc 'BlackJack' Rintsch wrote: ... > It's a feature. The `sys.stdout` object remembers if the last ``print`` > ended in a comma (see the `sys.stdout.softspace` attribute) and when the > interpreter executes its shutdown code and that `softspace` attribute is > set, an extra '\n' is printed. So

Re: Invoking Python from Cygwin problem.

2006-11-25 Thread Marc 'BlackJack' Rintsch
In <[EMAIL PROTECTED]>, Ant wrote: > -- > #!/usr/bin/python > print "Testing", > > Running the bash script, I get the following output: > > OKt var: Testing > Test var2: Test2 OK > > Does anyone have any idea why th

Invoking Python from Cygwin problem.

2006-11-24 Thread Ant
Hi all, Using cygwin and Python 2.5, I have the following scripts, one bash script and the other a python script: --- #!/bin/bash TEST_VAR=`./test.py` TEST_VAR2=Test2 echo "Test var: $TEST_VAR OK" echo "Test var2: $TEST_