Interesting. I can get that error by inserting a str() -- i.e. making that
line like the following:
print str(diffdir.stats.get_stats_logstring(_("Backup Statistics")))
But normally, it works for me. Your environment is UTF-8, so print
should be able to print the unicode. And xterm seems able to handle it
in my testing (didn't show unicode characters right, but it didn't die).
Do you have any ideas why your shell may not be able to handle unicode
output? How are you running duplicity?
** Changed in: duplicity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286845
Title:
Duplicity crashes with UnicodeEncode error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1286845/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
