[EMAIL PROTECTED] wrote:
> thanks for your input...
> well I just find out that modifying environment through ksh call is not
> possible (can't get the new evironment back to python).
I thought about this a few days ago. Can't you copy it like this:
import os
env_rows = os.popen('. some.script
(fup'2 set) In comp.unix.shell Donn Cave wrote:
> Portability [ksh]
> "echo" seems to mimic the behavior of sh on its host platform.
Rather: both usually mimic echo(1) - some shells even inspect PATH
(e.g. /usr/ucb/, /usr/5bin/ vs. /usr/bin/) and act accordingly.
--
http://mail.python.org/mailma
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> thanks for your input...
> well I just find out that modifying environment through ksh call is not
> possible (can't get the new evironment back to python). I think the
> best thing to do is to translate all my ksh to pure python... I tho
In article <[EMAIL PROTECTED]>,
Thorsten Kampe <[EMAIL PROTECTED]> wrote:
> * Cameron Laird (2005-06-02 18:08 +0100)
> > In article <[EMAIL PROTECTED]>,
> > Donn Cave <[EMAIL PROTECTED]> wrote:
> >>Meanwhile, it might be worthwhile to reconsider the use
> >>of ksh here, if you have any choice in
* Cameron Laird (2005-06-02 18:08 +0100)
> In article <[EMAIL PROTECTED]>,
> Donn Cave <[EMAIL PROTECTED]> wrote:
>>Meanwhile, it might be worthwhile to reconsider the use
>>of ksh here, if you have any choice in the matter. Ksh
>>is fine for interactive use, but has some unfortunate
>>flaws as a
thanks for your input...
well I just find out that modifying environment through ksh call is not
possible (can't get the new evironment back to python). I think the
best thing to do is to translate all my ksh to pure python... I thought
that I could re-use some stufff, but I guest I'm going to tran
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Cameron Laird)
wrote:
> In article <[EMAIL PROTECTED]>,
> Donn Cave <[EMAIL PROTECTED]> wrote:
> .
> .
> .
> >Meanwhile, it might be worthwhile to reconsider the use
> >of ksh her
In article <[EMAIL PROTECTED]>,
Donn Cave <[EMAIL PROTECTED]> wrote:
.
.
.
>Meanwhile, it might be worthwhile to reconsider the use
>of ksh here, if you have any choice in the matter. Ksh
>is fine for interactive use, but has
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
...
> I call it from python like that:
> -- begin ---
> import commands
> commands.getstatusoutput('. toto.env')
> -- end ---
>
> but it always return an error saying:
> sh: TOTO_ENV=/home/home: is not an identifier
>
> doesn anyone know w
