 |
 |
Indeed this should be handled by the experiment setup. They do calle different python versions from different releases as far I'm aware. The aspiration was to use only one version one day. cheers alessandra On 15/11/2012 16:03, John Gordon wrote: > Yesterday at GDB both LHCb and ATLAS mentioned supporting both Python 2.6 and 2.7. ATLAS said that setup.sh should allow an argument to specify the python version to use. > > That sounded like an aspiration not a solution they had today. > > -----Original Message----- > From: Testbed Support for GridPP member institutes [mailto:[log in to unmask]] On Behalf Of Matt Doidge > Sent: 15 November 2012 14:56 > To: [log in to unmask] > Subject: pythonpath & multiple pythons > > Hello all, > I hit a snag with testing the wn tarball which may or may not be a wider > issue with atlas jobs on emi - but it appears to me that some atlas > production jobs are attempting to `import lfc` using python26 as well > as/instead of regular python (2.4). > > The problem is that the when checking the modules in $PYTHONPATH python > just picks up the first thing that matches the name of what it wants to > load, and if that doesn't work it fails (or in the case of python26 > trying to load the 2.4 lfc modules that are in emi, python seg faults > unceremoniously). > > Is there a way to gracefully have python switch between which directory > to look up its modules depending on version, something other then the > clunky PYTHONPATH? And has anyone else been seeing these kind of > problems with their workers or possibly UIs? > > Thanks, > Matt > -Sad that he couldn't think up a decent flying circus quip, but > suspecting that they've all be done before. -- Facts aren't facts if they come from the wrong people. (Paul Krugman)