From: Keith Seitz <keiths@redhat.com>
To: Serhei Makarov <me@serhei.io>, Bunsen <bunsen@sourceware.org>
Subject: Re: Fwd: Re: [PATCH] Use binary mode to read .log/.sum
Date: Thu, 24 Sep 2020 10:47:33 -0700 [thread overview]
Message-ID: <4e5b855d-689d-6218-0df9-0174d5e87cdf@redhat.com> (raw)
In-Reply-To: <97957952-514b-4186-9cac-93fe07517309@www.fastmail.com>
On 9/23/20 6:00 PM, Serhei Makarov wrote:
> In retrospect, the need to deal with encodings is a major annoyance
> about I/O in recent Python versions. I have had to make prior fixes
> for similar issues, and I'm unsurprised that there is still more to
> fix.
I hear ya. Since I am no python expert, I just did some web searching
about the subject. This was the most recommended approach.
Thanks for the look -- patch pushed.
Keith
prev parent reply other threads:[~2020-09-24 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 1:00 Serhei Makarov
2020-09-24 17:47 ` Keith Seitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e5b855d-689d-6218-0df9-0174d5e87cdf@redhat.com \
--to=keiths@redhat.com \
--cc=bunsen@sourceware.org \
--cc=me@serhei.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).