Comment 42 for bug 1855736

I had/have similar issue as "resolved" in comment #25:

Initially, after building and installing version 0.8.09, I would try
duplicity --version
and get
Traceback (most recent call last):
  File "/usr/local/bin/duplicity", line 55, in <module>
    from duplicity.dup_main import main
ImportError: No module named 'duplicity'

I came upon this bug, saw comment #25 where it was suggested to change
the shebang to 'python3'. I checked, and mine was ALREADY saying 'python3', but
I changed it to 'python2' and then
duplicity --version responds correctly with
duplicity 0.8.09

If it helps, one of the first messages from running
$ sudo python setup.py install --prefix=/usr/local
is
/usr/lib/python2.7/dist-packages/setuptools/dist.py:333: UserWarning: Normalizing '0.8.09' to '0.8.9'
  normalized_version,

So it appears to be using python2 (2.7, to be exact) "during the build"?

Let me know if you'd like another bug open, or if there already is one to improve build scripts?
OR, better yet, maybe your "fix" was a fix for 0.8.10 and it has already been taken care of?

Thanks,