Comment 2 for bug 74956

Revision history for this message
Jan Mynarik (jan-mynarik) wrote :

I wrote "can't import module" and that is exactly the problem (only module names differ for different programs), e.g.

Traceback (most recent call last):
  File "/usr/bin/command-not-found", line 8, in <module>
    from CommandNotFound import CommandNotFound
ImportError: No module named CommandNotFound

I can change the interpreter by changing /usr/bin/python symbolic link to either python2.4 or python2.5. I did this hack because I really needed to run something (can't remember now) that didn't work with default python (set to 2.4).