> > The file pep_2777.py uses an encoding cookie that specifies UTF-8. > > Unfortunately my toolchain doesn't know about this, and displays it as > > Latin-1. > > What do you mean by "toolchain"? At the end of the chain is python, it > should know about this well enough. > > Did you try to open the file in IDLE? What other tools are you using? XEmacs. The particular version or configuration I'm using apparently doesn't recogize the coding cookie. > > Since the only UTF-8 is in 8-bit string literals (not Unicode > > literals), wouldn't it make more sense to drop the encoding cookie > > and use \xXX escapes in those literals? > > Having the original byte strings allows to verify correctness of the > test visually: the files created should look the same in the operating > system (using ls, or a file explorer) as they do in the source code. You could do this with a comment. --Guido van Rossum (home page: http://www.python.org/~guido/)
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