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 Thu, Aug 4, 2011 at 8:32 AM, Jerry Feldman <gaf at blu.org> wrote:
> On 08/04/2011 08:01 AM, Gordon Marx wrote:
>> On Thu, Aug 4, 2011 at 7:43 AM, Jerry Feldman <gaf at blu.org> wrote:
>>> Here at work, we encapsulate all products so the product does not depend
>>> on anything installed on the system (other than things like the kernel
>>> and libc. Compilers, languages like Perl and Python, libraries, such as
>>> cplex, et. al. I've probably got about 6 different copies of Python 2.6.
>>> I have no control of this since this is done in Toronto.
>> We don't go that far, but we do the same sort of thing -- don't rely
>> on the system, everything gets installed in a custom directory
>> structure, so there are machines on our network that have
>> /blah/bin/python2.{4,5,6,7}. That way, at least you only have one copy
>> of Python2.6 that everyone can use.
>>
> Normally at a client installation, the client would source a
> configuration file (either bash or cshrc) to get all the appropriate
> environment variables. It gets more complicated when my coworker is
> building some scripts that are executed in a user environment.

Right, but if you guarantee that there will be a python2.6 interpreter
at a given path, you don't need any environment variables to tell you
where it is.



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 / webmaster@blu.org