Comment 20 for bug 340394

Tim пишет:
> Hi Alexander,
> I checked your hints.
> The result ("s") is what I was aiming at.
> Thanks a lot for this workaround.
>
> I still do not consider this bug solved:
> 1) next to the standalone windows installer I have to take care now that bzrlib is available

You can use installed bzr.exe and its bzrlib if you're using Python 2.5.
I can teach you if you wish.
But AFAICS you're using Python 2.6, so it won't work.

> 2) I consider
> p_log = subprocess.Popen(('bzr log --short'),
> stdout=subprocess.PIPE, stderr=subprocess.PIPE, bufsize=-1)
> as faster.

I don't quite understand this.

> 3) why these encoding problems?

Because bzr:

a) written mostly by ASCII-only people who don't see all these unicode
problems every day?
b) written by Linux developers who have utf-8 as their standard encoding
everywhere and therefore always have utf-8 output and don't encounter
UnicodeErrors?

> As a suggestion:
> Incorporate your code in the "bzr log" command:
> bzr log --export-encoding "utf-8" --file-name "mylog.txt"

My code is far from this.

> and everyone is happy and this bug could be closed.

I can help you write plugin to do this. It will be much simpler better
and easier to achieve. I don't do bzr development on regular basis, and
I'm doubt anyone else will implement this. If you wish I can guide you
in writing such patch for bzr. But writing plugin is really simpler.