Dear Alain, Thanks very much for the information on this bug.
I think that since salomeloader is a script, maybe we can patch that script to set the PYTHONPATH variable. That way we don't htave to have too many files in dist-packages, and a non-expert user can run it. What do you think? -Adam On Wed, 2010-09-29 at 17:04 +0200, Alain Leufroy wrote: > Hi Adam, > > I've worked a little bit on this problem with André. > > We see that the problem is about the fact that the Salome python modules site > in > the ``salome/`` directory whereas it is not interpreted as a package by python > (``salome/__init__.py`` is missing) and all python code import these modules > directly. > As a consequence the ``salome/`` directory must be added to the PYTHONPATH (as > done in runSalome). > > But when calling ``salomeloader`` the PYTHONPATH was not modified. > We found two kinds of solution. > > 1. Letting the install as clean as it is and expecting that advanced user > correctly set the PYTHONPATH: > > ex: > > $ PYTHONPATH=/usr/lib/python2.6/dist-packages/salome/ salomeloader > > > 2. Putting all the salome python modules directly in the standard site > packages > ($prefix/lib/python/dist-packages/ instead of > $prefix/lib/python/dist-packages/salome). This allow to run ``salomeloader`` > directly but the install will mess with every (too many ?) salome internal > modules. And we may get potential conflicts. > In order to achieve this, you can add: > > ``mv ../debian/salome/usr/lib/python*/*-packages/salome/* > ../debian/salome/usr/lib/python*/*-packages/`` > to debian/rules after installation. > > > Which solution suits you as you are the debian package maintainer? > > Cheers, > > Alain -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
signature.asc
Description: This is a digitally signed message part
