Alain,
Panda catches this and throws an error. I have a work
around -- I dump the path, delete the reference
to the non-existent directory, and reassign the
PYTHONPATH. Its rather messy.
I would like to encourage my usatlas colleagues to use
osg-client rather than lcg-client... just in the mail
over the weekend was someone telling us atlas
physicists to setup their grid environment with:
====
6. Setup Grid and do a "grid-proxy-init":
$ source /afs/usatlas.bnl.gov/lcg/current/etc/profile.d/grid_env.sh
$ grid proxy-init
====
I'd like to correct this, to have them install osg-client,
but at the moment Panda would fail for a trivial reason.
Rob
On Feb 8, 2008, at 2:25 PM, Alain Roy via RT wrote:
>> [rwg@hep.uchicago.edu - Thu Feb 07 22:36:23 2008]:
>>
>> Alain
>>
>> It matters, because it gets put into the python path of
>> a Panda application (pathena). That program senses
>> the fact that ../globus/lib64 doesn't exist, and quits.
>>
>> I think people have not complained about this since
>> they typically use glite middleware (sitting in an AFS
>> area at either CERN or BNL) for the client tools.
>> I am trying to establish a "clean" interactive
>> environment for US ATLAS using OSG client, so
>> this is an obstacle to that.
>
> Ah, I see.
>
> Can you clarify if this is a Python problem or a Panda problem? I
> ran a
> basic Python script with a PYTHONPATH that included a non-existant
> directory and it didn't have any problems.
>
> I think I know how to address this. How serious is this for you? Do we
> need to get a fix into VDT 1.8.1, or is the next release of the VDT
> soon
> enough for you?
>
> As a workaround, there is a place you can override the PYTHONPATH
> set by
> the VDT to remove the bad directory. If you want help with this
> option,
> I'm happy to help work it out.
>
> -alain
>
>
> --
> View ticket at <http://vdt.cs.wisc.edu/rt/Ticket/Display.html?
> user=guest&pass=guest&id=3299>
> VDT Support, vdt-support@ivdgl.org