Martin v. Löwis wrote:
> Reinhold Birkenfeld wrote:
>> One problem is that no Unicode escapes can be used since compiling
>> the file raises ValueErrors for them. Such strings would have to
>> be produced using unichr().
>
> You mean, in Unicode literals? There are various approaches, depending
>
Reinhold Birkenfeld <[EMAIL PROTECTED]> writes:
> Hi,
>
> I looked whether I could make the test suite pass again
> when compiled with --disable-unicode.
>
> One problem is that no Unicode escapes can be used since compiling
> the file raises ValueErrors for them. Such strings would have to
> be p
Reinhold Birkenfeld wrote:
> One problem is that no Unicode escapes can be used since compiling
> the file raises ValueErrors for them. Such strings would have to
> be produced using unichr().
You mean, in Unicode literals? There are various approaches, depending
on context:
- you could encode the
Hi,
I looked whether I could make the test suite pass again
when compiled with --disable-unicode.
One problem is that no Unicode escapes can be used since compiling
the file raises ValueErrors for them. Such strings would have to
be produced using unichr().
Is this the right way? Or is disabling
