progress.py: old_div not defined
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Duplicity |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Every time I run duplicity (revision 1401), I get the following exception in the middle of the output.
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/local/
self.run()
File "/usr/local/
tracker.
File "/usr/local/
self.
NameError: name 'old_div' is not defined
The problem seems to go away when I replace `old_div(a,b)` with `a/b`, but I'm not sure if the fix is that simple.
| Charles Celerier (chckyn) wrote | #1 |
| Changed in duplicity: | |
| importance: | Undecided → Medium |
| milestone: | none → 0.8.02 |
| status: | New → Fix Committed |
| Changed in duplicity: | |
| status: | Fix Committed → Fix Released |
I also get a broken progress bar. At the end of each backup when the data is uploading to S3, I always see something like this where the progress bar never moves past 0%.
Processed volume 2
Writing duplicity-
Uploading s3+http://
3.2MB 00:00:18 [326.0KB/s] [> ] 0% ETA 9sec
16.9MB 00:00:21 [1.6MB/s] [> ] 0% ETA 12sec
20.7MB 00:00:24 [1.5MB/s] [> ] 0% ETA 15sec
AsyncScheduler: scheduling task for asynchronous execution
32.1MB 00:00:27 [2.2MB/s] [> ] 0% ETA < 30sec
45.6MB 00:00:30 [2.9MB/s] [> ] 0% ETA < 30sec
61.5MB 00:00:33 [3.6MB/s] [> ] 0% ETA < 30sec
80.4MB 00:00:36 [4.4MB/s] [> ] 0% ETA < 30sec
98.0MB 00:00:39 [4.8MB/s] [> ] 0% ETA < 30sec
115.1MB 00:00:42 [5.1MB/s] [> ] 0% ETA < 45sec
129.0MB 00:00:45 [5.0MB/s] [> ] 0% ETA < 45sec
141.8MB 00:00:48 [4.8MB/s] [> ] 0% ETA < 45sec
156.9MB 00:00:51 [4.8MB/s] [> ] 0% ETA < 45sec
171.2MB 00:00:54 [4.8MB/s] [> ] 0% ETA < 45sec
183.4MB 00:00:57 [4.6MB/s] [> ] 0% ETA < 1min
197.6MB 00:01:00 [4.6MB/s] [> ] 0% ETA < 1min
Deleting /var/folders/
AsyncScheduler: task execution done (success: True)