"M.-A. Lemburg" wrote: > >... > Since Python source code is defined to be ASCII, the Unicode literal > encodings (both standard and raw) should be supersets of ASCII and > match the encoding used elsewhere in the program text, e.g. in > comments and maybe even 8-bit strings (even though their encoding > is only implicit and completely under the programmer's control). Python programmers do not read PEPs to learn how to use new features. I think it makes the whole thing much simpler if we define it on the file level explicitly. To me, the feature is most helpful if it helps the interpreter and various code inspection tools to understand all of the non-ASCII information in the file. -- Take a recipe. Leave a recipe. Python Cookbook! http://www.ActiveState.com/pythoncookbook
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