[Python-3000] PEP: Supporting Non-ASCII Identifiers

["Martin v. Löwis"]

> It seems to me the simplest thing to do is to require that Python
> source files be normalized.  Then the ambiguity just goes away.
> Everyone knows what form their files should be in, and if you really
> need to construct a non-normalized string, you can do that explicitly
> using "\u" notation.

However, what would that mean wrt. non-Unicode source encodings.

Say you have a Latin-1-encoded source code. Is that in NFC or not?

Regards,
Martin