[Bigjob-users] Removal of BigJob in CSA installation

[Andre Luckow]

Hi Andre,
yes setting up the PATH right would work, but it is quite error-prone
and difficult to debug. For example, if you spawn a BJ to a remote
resource where the PATH stuff is differently setup you end up with a
mess.

That's why we would prefer to have the user explicitly add BJ. This
way it can be ensured that the user uses the BJ it wants to use and
NOT accidentally ends up using the one that comes with CSA (which is
already several versions behind the current PyPi release). We already
had several issues related to the usage of different BJ versions in
the same app.

Making things explicit really would help!

Thanks,
Andre

On Fri, Dec 9, 2011 at 12:15 PM, Andre Merzky <andremerzky at gmail.com> wrote:
> Hi Andre,
>
> On Thu, Dec 8, 2011 at 10:27 PM, Andre Luckow <aluckow at cct.lsu.edu> wrote:
>> Hi Andre,
>> can we separate the Path where BJ is installed from the default SAGA
>> PYTHONPATH.? This way the user can easily remove BJ from the PATH, but
>> still use SAGA?
>
> isn't the PYTHONPATH order-dependent, in the sense that
>
>  PYTHONPATH=$HOME/bj_new/:$SAGA_LOCATION/lib/python1.7/site-packages
>
> would prefer bigjob from $HOME/bj_new?
>
> Best, Andre.
>
>
>> Thanks!
>> Andre
>>
>> On Thu, Dec 8, 2011 at 10:25 PM, pradeep kumar Mantha
>> <pradeepm66 at gmail.com> wrote:
>>> Hi!
>>>
>>>          Given the simplicity of installation of BigJob, I think the system
>>> installation of BigJob is not required anymore. The main problem being faced
>>> is to use latest version of BigJob when old system installation is still
>>> present. The user has to tweak the BigJob( manager & agent) code by setting
>>> the PYTHONPATH to use latest version of  BigJob installed in user space.
>>>
>>> thanks
>>> pradeep.
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Bigjob-users mailing list
>>> Bigjob-users at mail.cct.lsu.edu
>>> https://mail.cct.lsu.edu/mailman/listinfo/bigjob-users
>>>
>
>
>
> --
> Nothing is ever easy...