From: Tom Tromey <tromey@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [python] Fix Python 3 build and testsuite issues
Date: Wed, 21 Aug 2013 14:59:00 -0000 [thread overview]
Message-ID: <8761uzf5t3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5214CECF.30103@redhat.com> (Phil Muldoon's message of "Wed, 21 Aug 2013 15:29:35 +0100")
Phil> Strings in Python 3 are now always encoded and are encapsulated by the
Phil> "str" class.
Phil> In Python 2 you had str() and unicode(), where unicode was encoded and
Phil> str just represented bytes (IE just an unencoded string).
Phil> Reading around the suggestion seems to be to do this:
Phil> try:
Phil> # basestring catches both types of Python 2.x strings
Phil> if isinstance(sym, basestring)
Phil> return True
Phil> except NameError:
Phil> # If we are here, basestring does not exist, so Python 3.x
Phil> if isinstance(sym, str)
Phil> return True
Phil> # Continue to process objects that are not a string.
We can do this check once, at top-level:
try:
if isinstance('hi', basestring):
def is_string(x):
return isinstance(x, basestring)
except NameError:
def isinstance(x):
return isinstance(x, str)
Maybe duck typing is still preferable though.
Not sure if this needs a third def in case the 'if' fails without throwing.
Probably not.
Tom
next prev parent reply other threads:[~2013-08-21 14:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 14:50 Phil Muldoon
2013-08-19 16:19 ` Tom Tromey
2013-08-19 16:45 ` Phil Muldoon
2013-08-19 18:34 ` Tom Tromey
2013-08-20 19:43 ` Phil Muldoon
2013-08-20 19:59 ` Tom Tromey
2013-08-20 20:32 ` Phil Muldoon
2013-08-21 14:29 ` Phil Muldoon
2013-08-21 14:59 ` Tom Tromey [this message]
2013-08-21 15:37 ` Paul_Koning
2013-08-21 15:42 ` Tom Tromey
2013-08-21 14:56 ` Tom Tromey
2013-08-22 10:46 ` Phil Muldoon
2013-08-27 15:41 ` Tom Tromey
2013-08-29 10:08 ` Phil Muldoon
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=8761uzf5t3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
/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