Hi Roman,
* Roman Z. , 2011-11-10, 14:09:
ranger can't run if it can't find the "ranger" python module. It must
be in one of the PYTHONPATH directories. On my install, ranger was
installed to /usr/share/pyshared
Which is completely normal.
which is not in PYTHONPATH so ranger will not find
Hi Raphael,
* Raphael Plasson , 2011-09-29, 18:06:
ranger can actually be launched normally if the link /usr/bin/python is
changed, and point to /usr/bin/python/2.6 instead of the now default
/usr/bin/python/2.7.
Please never ever change the /usr/bin/python symlink destination
manually. More
Dear fellows,
ranger can't run if it can't find the "ranger" python module. It must
be in one of the PYTHONPATH directories. On my install, ranger was
installed to /usr/share/pyshared which is not in PYTHONPATH so ranger
will not find it. It ought to be put at /usr/lib/pythonX/dist-packages/
in
Hello,
I can reproduce the bug.
Linking python to python2.6 instead of python2.7 works indeed.
Cheers,
--
Steve
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Package: ranger
Version: 1.4.3-1
Severity: grave
Justification: renders package unusable
Hello,
ranger cannot be launched since the default python switched from 2.6 to
2.7. After the python upgrade, calling ranger in commandline gives:
Traceback (most recent call last):
File "/usr/bin/ranger",
5 matches
Mail list logo
