Hi,
On 04/08/2019 08:59, Eric L. wrote:
> OK, I've created a sub-branch ericzolf-py2to3-bytes and will work on
> this aspect, moving away from str for paths to bytes.
If someone is interested, there is a working version at
https://github.com/ericzolf/rdiff-backup/tree/ericzolf-py2to3-bytes
You
Hi,
On 03/08/2019 14:50, Robert Nichols wrote:
>> The way to work around this in rdiffweb at least it's to manage path as
>> bytes. That is how rdiffweb 1.2.8 is working. Path are bytes. That is
>> also
>> how most filesystem are working too. Paths are bytes and those are
>> decoded
>> to be
On 8/3/19 6:49 AM, Patrik Dufresne wrote:
Hello Éric, im very concerned about this. I did not review all your
changes, and did not notice this fact. I'm backup allot of various system
and the encoding are not all utf8. And invalid utf8 happen quite often.
The way to work around this in rdiffweb
Hello Éric, im very concerned about this. I did not review all your
changes, and did not notice this fact. I'm backup allot of various system
and the encoding are not all utf8. And invalid utf8 happen quite often.
The way to work around this in rdiffweb at least it's to manage path as
bytes. That
Hi,
as I worked on migrating to Python 3, one of the "fanciest" aspects was
the change from str/unicode to bytes/str "character chains" types.
Without going into the technical details (python savvy persons will know
what I mean), it means among other things that the codeset of file names
becomes
