On Wed, 17 May 2000, Fredrik Lundh wrote: > the main reason for that is that Python 1.6 doesn't have any way to > specify source encodings. add that, so you no longer have to guess > what a string *literal* really is, and that problem goes away. but You seem to be familiar with the Tcl work, so I'll ask you this question: Does Tcl have a way to specify source encoding? I'm not aware of it, but I've only had time to follow the Tcl world very lightly these past few years. ;) -Fred -- Fred L. Drake, Jr. <fdrake at acm.org>
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