[Pythonmac-SIG] (no subject)

[konrad.hinsen@laposte.net]

On May 10, 2005, at 19:21, Bob Ippolito wrote:

>> My particularly good reason is that I set PYTHONPATH differently in
>> different shell environments for testing purposes. Changing links and 
>> path
>> files is a lot more work.
>
> I use different checkouts (or python interpreters) for different 
> environments...

That's no so straightforward for me as my environment is mixed, Mac and 
Linux. Much of the code resides on a shared NFS partition. That's why I 
need the one feature that PYTHONPATH provides and that .pth files 
don't: environment variables in the path definitions.

> Well I went ahead and changed the default behavior to ignore 
> PYTHONPATH.

Great!

> However, I still don't quite agree with you.  There are PLENTY of 
> environment variables that you should only set if you know what you're 
> doing, and you should only set as a software developer.  The DYLD 
> variables come to mind.  Setting

I even agree - but many others apparently don't.

> A system administrator should never, ever, be setting PYTHONPATH.

Most of the Unix machines I have worked on have PYTHONPATH set globally 
to something. I suppose the administrator's point of view is that 
Python is part of the system, users are not supposed to have their own 
installation. Which for most users is probably right.

I don't know what the typical situation on the Mac is, but I tend to 
view the Mac as part of the big Unix family.

Konrad.
--
---------------------------------------------------------------------
Konrad Hinsen
Laboratoire Léon Brillouin, CEA Saclay,
91191 Gif-sur-Yvette Cedex, France
Tel.: +33-1 69 08 79 25
Fax: +33-1 69 08 82 61
E-Mail: khinsen at cea.fr
---------------------------------------------------------------------