thomas wrote:
> > I'm currently seeing a failure in test_ucn:
> >
> > test test_ucn crashed -- exceptions.UnicodeError: Unicode-Escape decoding
> > error: Illegal Unicode character
> >
> > It looks like one of the unicode literals in test_ucn is invalid, but it's
> > damned hard to pin down which:
>
> Feels to me like there's a bug in the string literal processing that
> makes *any* string literal containing \N{...} fail during code
> generation.
I took another look at the error message: the only explanation
I can see here is that the lookup succeeds, but the call to ucn-
hash returns a value larger than 0x10ffff.
What is Py_UCS4 set to under gcc?
Confusing /F
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4