Re: [Duplicity-talk] ImportError (progress) when setting up for development

[Michael Terry]

You might need to run like:

PYTHONPATH=. ./bin/duplicity

On 6 September 2014 17:34, Aaron Whitehouse <address@hidden> wrote:

Hi,

I'm wanting to try to do a little development on duplicity, but I am struggling to get it set up. Apologies if this is a stupid question, but I'm new to some of these tools.

I'm following the instructions at:
http://bazaar.launchpad.net/~duplicity-team/duplicity/0.7-series/view/head:/README-REPO

==
1) Do the checkout while in a location called $DUP_ROOT:
        bzr lp:duplicity . [for the dev branch]
   -OR- bzr lp:duplicity/stable . [for the stable branch]
==
so I do:
:~/Programming$ bzr lp:duplicity .
bzr: ERROR: unknown command "lp:duplicity"

:~/Programming$ bzr branch lp:duplicity .
bzr: ERROR: Target directory "." already exists.

I therefore assume that this should be "bzr branch lp:duplicity":
:~/Programming$ bzr branch lp:duplicity
Branched 998 revisions.

==
2) cd $DUP_ROOT/duplicity
3) run "python compilec.py" to create _librsync.so
==
:~/Programming/duplicity/duplicity$ python compilec.py
running build
running build_ext
building '_librsync' extension
creating build
creating build/temp.linux-x86_64-2.7
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c _librsyncmodule.c -o build/temp.linux-x86_64-2.7/_librsyncmodule.o
creating build/lib.linux-x86_64-2.7
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security build/temp.linux-x86_64-2.7/_librsyncmodule.o -lrsync -o build/lib.linux-x86_64-2.7/_librsync.so

==
4) cd ..
5) run "./bin/duplicity -V". You will see "duplicity $version" instead
of the normal version number. Versioning comes during the release.
==
:~/Programming/duplicity/duplicity$ cd ..
:~/Programming/duplicity$ ./bin/duplicity -V
Traceback (most recent call last):
  File "./bin/duplicity", line 56, in <module>
    from duplicity import progress
ImportError: cannot import name progress

Running the unit tests seems to work (cd testing; ./run-tests) and nearly everything finishes with "ok" (except 2to3, diff2, PEP8, pylint and 2.6 tests, as I only have 2.7 installed).

Any thoughts would be appreciated.

This started out on Launchpad answers: https://answers.launchpad.net/duplicity/+question/252898

Many thanks in advance,

Aaron

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk