On 01/10/2007, Nick Maclaren <nmm1 at cus.cam.ac.uk> wrote: > So, damn the outside system, EXACTLY what does Python mean by > such characters, and EXACTLY what uses of them are discouraged > as having unspecified meanings? If we could get an answer to > that precisely enough to write a parse tree with all terminals > explicit, this problem would go away. Python, the language, means nothing by the characters. They are bytes with defined values in a byte string (in 2.x, in 3.0 they are Unicode characters, but otherwise no difference). The *language* places no interpretation on them. Certain library functions place an interpretation on the byte values, but you need to read the function definition for that. And (a) they may not all be consistent, and (b) they may say "follows platform behaviour", but that's the way it is, so you have to live with it. Paul.
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