Bug 6542 - external python modules fail to compile to pyc if \\N escapes are used
Summary: external python modules fail to compile to pyc if \\N escapes are used
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-11 11:11 UTC by Gernot Vormayr
Modified: 2014-02-20 08:19 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Change always disabled unicodedata to conditionally disabled for python-host (567 bytes, patch)
2013-10-11 11:11 UTC, Gernot Vormayr 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gernot Vormayr 2013-10-11 11:11:50 UTC 
Created attachment 5066 [details]
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.
Comment 1 Thomas De Schampheleire 2014-02-07 10:18:26 UTC 
Patch updated with python3 changes, and sent to the list, awaiting integration.
Comment 2 Thomas De Schampheleire 2014-02-20 08:19:30 UTC 
Problem fixed with commit http://git.buildroot.org/buildroot/commit/?id=c3d539b53ff0533e91ae849dbdcdd589b0fec0cc

Thanks for reporting!