| Summary: | external python modules fail to compile to pyc if \\N escapes are used | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Gernot Vormayr <gvormayr> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | buildroot, gvormayr |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: | Change always disabled unicodedata to conditionally disabled for python-host | ||
Patch updated with python3 changes, and sent to the list, awaiting integration. Problem fixed with commit http://git.buildroot.org/buildroot/commit/?id=c3d539b53ff0533e91ae849dbdcdd589b0fec0cc Thanks for reporting! |
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.