From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6542] New: external python modules fail to compile to pyc if \\N escapes are used
Date: Fri, 11 Oct 2013 11:11:51 +0000 (UTC) [thread overview]
Message-ID: <bug-6542-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6542
Summary: external python modules fail to compile to pyc if \\N
escapes are used
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: gvormayr at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5066
--> https://bugs.busybox.net/attachment.cgi?id=5066
Change always disabled unicodedata to conditionally disabled for python-host
The Host python used to bytecompile modules is always compiled with
disable-unicodedata regardless of the BR2_PACKAGE_PYTHON_UNICODEDATA setting.
If a python-module is compiled to a pyc-file and the py file contains \N{name}
escapes this compilation will fail with:
"\\N escapes not supported (can't load unicodedata module)"
Which further leads to missing files if pycs are used in the target-image.
Attached changes always disabled to conditionally disabled depending on
BR2_PACKAGE_PYTHON_UNICODEDATA.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-10-11 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 11:11 bugzilla at busybox.net [this message]
2014-02-07 10:18 ` [Buildroot] [Bug 6542] external python modules fail to compile to pyc if \\N escapes are used bugzilla at busybox.net
2014-02-20 8:19 ` bugzilla at busybox.net
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=bug-6542-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.