I use a mainly stable AMD64 box. Whenever I launch pymol (stable 1.2.1 or ~amd64 1.2.2) I get this error: === $ pymol /usr/bin/python2.6: can't open file '/__init__.py': [Errno 2] No such file or directory === However, pymol-1.2.x emerges finely. What surprises me is that pymol-1.2.1 is stable for amd64, as well as python-2.6.4. Reproducible: Always
can't open file '/__init__.py': [Errno 2] No such file or directory That is quite interesting ... of course there is no such file! So the question is - why does that path not get expanded properly? And how did you manage to trigger this behaviour?
# cat /usr/bin/pymol #!/bin/sh python -O ${PYMOL_PATH}/__init__.py $* and PYMOL_PATH is defined in /etc/env.d/20pymol.
Did you run source /etc/profile in the shell you wanted to start pymol?
(In reply to comment #3) > Did you run > > source /etc/profile > > in the shell you wanted to start pymol? > No, I didn't. I have just tried pymol after restarting my laptop (because I took it somewhere else) and pymol now starts beautifully. Maybe a warning after emerging it is necessary? I would have never guessed I needed to source my /etc/profile to make it work Anyway, thanks very much for your help and efforts.
