From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] bintree.populate: binhost connection failure triggers TypeError (bug 532784)
Date: Sun, 3 May 2015 23:48:47 -0700 [thread overview]
Message-ID: <20150503234847.712df520.dolsen@gentoo.org> (raw)
In-Reply-To: <554713C0.7070505@gentoo.org>
On Sun, 03 May 2015 23:37:52 -0700
Zac Medico <zmedico@gentoo.org> wrote:
> On 05/03/2015 11:25 PM, Brian Dolbec wrote:
> > Isn't this backwards from what was reported. It generated a
> > UnicodeDecodeError when using additional args to unicode().
>
> It was actually a TypeError.
>
> > It needed
> > to convert it to string so errors= needed to not be passed in.
>
> Yeah, the first unicode call fixes that.
>
> If a UnicodeDecodeError is then raised (not a TypeError), the second
> unicode call decodes the UnicodeError.object attribute, which is
> guaranteed to be a string that can be passed to unicode using the
> three argument form.
OK then :)
--
Brian Dolbec <dolsen>
prev parent reply other threads:[~2015-05-04 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 4:52 [gentoo-portage-dev] [PATCH] bintree.populate: binhost connection failure triggers TypeError (bug 532784) Zac Medico
2015-05-04 6:25 ` Brian Dolbec
2015-05-04 6:37 ` Zac Medico
2015-05-04 6:48 ` Brian Dolbec [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=20150503234847.712df520.dolsen@gentoo.org \
--to=dolsen@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/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