From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] host python/python3: conditionally disable unicodedata
Date: Fri, 7 Feb 2014 11:28:19 +0100 [thread overview]
Message-ID: <20140207112819.2fab19a3@skate> (raw)
In-Reply-To: <e06b104c5f166c541741.1391768165@argentina>
Dear Thomas De Schampheleire,
On Fri, 07 Feb 2014 11:16:05 +0100, Thomas De Schampheleire wrote:
> The host python always had --disable-unicodedata, regardless of the
> corresponding configuration option BR2_PACKAGE_PYTHON_UNICODEDATA.
> Since the host python is used to byte-compile python modules, this meant
> that such modules could not contain unicode strings. For example, following
> statement in a python module:
> print u"\N{SOLIDUS}"
>
> would cause the byte-compilation to fail with message:
> SyntaxError: ("(unicode error) \\N escapes not supported (can't load
> unicodedata module)",
>
> Instead, conditionally disable unicodedata based on
> BR2_PACKAGE_PYTHON_UNICODEDATA, also for the host python.
>
> This fixes bug #6542 (https://bugs.busybox.net/show_bug.cgi?id=6542)
>
> Reported-by: Gernot Vormayr <gvormayr@gmail.com>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
For information, my upcoming patch series that bumps Python uses
--enable-unicodedata unconditionally for the host python, because
recent versions of python-setuptools need unicodedata.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-07 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 10:16 [Buildroot] [PATCH] host python/python3: conditionally disable unicodedata Thomas De Schampheleire
2014-02-07 10:28 ` Thomas Petazzoni [this message]
2014-02-13 9:15 ` Thomas De Schampheleire
2014-02-13 9:30 ` Thomas Petazzoni
2014-02-14 20:41 ` Thomas De Schampheleire
2014-02-18 22:10 ` Peter Korsgaard
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=20140207112819.2fab19a3@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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