On 2010/5/21 John Griessen wrote: > Denis Barbier wrote: >> I have some trouble with python 2.6, it seems that extensions are not >> loaded, no idea why yet. > > This excerpt from debian policy, > http://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html, > seems complicated and has to do with it: > > "Directories with private Python modules must be absent from the sys.path. > Public Python modules not handled by python-central or > python-support must be installed in the system Python modules directory, > /usr/lib/pythonX.Y/dist-packages for python2.6 and later, > and /usr/lib/pythonX.Y/site-packages for python2.5 and earlier. As an > exception to the above, modules managed by python-support > are installed in another directory which is added to the sys.path using the > .pth mechanism. The .pth mechanism is documented in > the Python documentation of the site module. A special directory is dedicated > to public Python modules installed by the local > administrator, /usr/local/lib/pythonX.Y/dist-packages for python2.6 and > later, and /usr/local/lib/pythonX.Y/site-packages for > python2.5 and earlier. "
I called 'python2.6 setup.py install --user' which installs modules under $HOME/.local/lib/python2.6/, this is exactly what I want to achieve, being able to install as a normal user. This quoted text does not mention that, thus I tried 'sudo python2.6 setup.py install' to install files user /usr/local/lib/python2.6/dist-packages/ but the result is the same. There is one strange problem, there is no OCC/__init__.py in both installations, no idea why. I ran build+install again, and everything works now. Yeepee. Denis _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
