Merge lp:~mterry/duplicity/gio_child_for_display_name_0.7 into lp:~duplicity-team/duplicity/0.7-series
Status: | Merged |
---|---|
Merged at revision: | 1308 |
Proposed branch: | lp:~mterry/duplicity/gio_child_for_display_name_0.7 |
Merge into: | lp:~duplicity-team/duplicity/0.7-series |
Diff against target: |
44 lines (+5/-7) 1 file modified
duplicity/backends/giobackend.py (+5/-7) |
To merge this branch: | bzr merge lp:~mterry/duplicity/gio_child_for_display_name_0.7 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+329050@code.launchpad.net |
Description of the change
A minor improvement to my recent display_name patch for the GIO backend. Since we now get a list of display names from GIO, it only makes sense that we ask for new files with the get_child_
I know of no bugs doing what we were doing (any file we request should be simple ASCII -- and this API is mostly for using utf8 strings instead of bytecode strings). But some backends, like google-drive: have vastly different concepts of name vs display name. The google-drive: backend currently accepts either in get_child(), but maybe one day it (or a similar bizarre backend) will be more pedantic.
So let's just use the more correct API now before it becomes a problem.