argv[0] manipulation

Dennis Lee Bieber wlfraed at ix.netcom.com
Thu Dec 12 20:21:19 EST 2002


Robin Munn fed this fish to the penguins on Thursday 12 December 2002 
07:32 am:

> 
> My PATH contains '/home/rmunn/bin' and does NOT contain '.'. Therefore
> I conclude that ksh *does* prepend the appropriate dir to argv[0],
> and/or that I must have misunderstood what you are saying.
> Explanations, please?

[wulfraed at beastie wulfraed]$ vi bin/test.py
[wulfraed at beastie wulfraed]$ chmod a+x bin/test.py
[wulfraed at beastie wulfraed]$ bin/test.py
['bin/test.py']
[wulfraed at beastie wulfraed]$ PATH=~/bin:$PATH; export PATH
[wulfraed at beastie wulfraed]$ test.py
['/home/wulfraed/bin/test.py']

        Looks like BASH handles it that way.

        Hmm... I used to use tcsh a decade ago (on my Netcom shell account it 
gave similar syntax as my Amiga command line interpreter); 
unfortunately it has been too long for me to try setting up a test here.

-- 
 > ============================================================== <
 >   wlfraed at ix.netcom.com  | Wulfraed  Dennis Lee Bieber  KD6MOG <
 >      wulfraed at dm.net     |       Bestiaria Support Staff       <
 > ============================================================== <
 >        Bestiaria Home Page: http://www.beastie.dm.net/         <
 >            Home Page: http://www.dm.net/~wulfraed/             <




More information about the Python-list mailing list