Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] Python script question

On Wed, Aug 03, 2011 at 10:28:20AM -0400, Jerry Feldman wrote:
> A coworker of mine has a Python script set up as:
> #! $PATH_TO_PYTHON/python
> ... python code
> It is not unusual to have commands like this. Mailman does this with
> several of its commands. The issue here is that he needs to use an
> environment variable to call the python interpreter. We certainly can do
> it a messy way:
> #! /bin/bash
> $PATH_TO_PYTHON/python
> But this would require a wrapper script.
> Or he can use an explicit path to the python interpreter.
> #! /usr/bin/python
> The problem here is that the version of python he uses MUST be
> encapsulated in our company's product.
> #! /mnt/fubar/versionxyz/bin/python
> But this will possibly differ with each release of our company's product
> since we maintain a number of releases here.  Some other solutions is to
> set up symlinks in the local directory. 
> Any ideas on how to get the loader to expand the environment variable
> after the #!??

You can't do that, because it's parsed by the kernel, not the

Here's my suggestion:

create /mnt/fubar/product-current as a link to

and maintain that.

Now your script can start:


Alternatively, install your python script in

and start with:


(I just tested that, and it works.)


-- is hereby incorporated by reference.
You can't fight for freedom by taking away rights.

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /