When a BuildException occurs and it contains non-ascii characters,
utils.spaces called from tool.show_report fails because it tries to join a
non-encoded string with '\n' which is a unicode literal.
Additionally if this is fixed, writing it to sys.stdout.write will fail, since it the encoding is not properly
handled. (Is there a reason to not use print or logging?)
This can actually occur when gcc outputs unicode ticks for variable names. Odd.
When a BuildException occurs and it contains non-ascii characters,
utils.spacescalled fromtool.show_reportfails because it tries to join a non-encoded string with '\n' which is a unicode literal.Additionally if this is fixed, writing it to
sys.stdout.writewill fail, since it the encoding is not properly handled. (Is there a reason to not use print or logging?)This can actually occur when gcc outputs unicode ticks for variable names. Odd.