Sort out weirdness with condor python bindings

PerilousApricot / CRAB3-GlideinWMS-Meta

Meta-package for CRAB3-GideinWMS development

0 stars 0 forks source link

Sort out weirdness with condor python bindings #1

Open PerilousApricot opened 11 years ago

PerilousApricot commented 11 years ago

So far, there's a few issues with the condor python bindings we need to check out/possibly push upstream

import htcondor dies if CONDOR_CONFIG env variable doesn't exist. It does _exit() so it's untrappable
How should we manage different endianness/versions of python/condor? If we pull and override the local python install with one bootstrapped from CMS, how can we best hope that CMS's python will be compatible with the site's htcondor libraries? Could we maybe a few versions of the classad module put in cvmfs?

bbockelm commented 11 years ago

First one is fixed - CONDOR_CONFIG is set by the wrapper script.

Second one - I don't think this is a problem long-term. We can always ask the schedd to provide condor python libs or ship them with CMSSW. I have ones that integrate with the CMSSW python in the tarball.

One thing we don't do - after importing htcondor, we should remove the condor libraries from our path. Particularly, lib/condor includes a bunch of globus libs which interfere with the host's gsissh client.