Raymond Hettinger wrote: > [MAL] > >>Second, it is good design and good practice to store text >>data in Unicode objects, because that's what they were designed for, >>while string objects have always been an abstract container for >>storing bytes with varying meanings and interpretations. Hmm, I wonder why you cut away the first part: "First, please be aware that normal use of Templates is for formatting *text* data." This is the most important argument for making Template a Unicode-subclass. Coercion to Unicode then is a logical consequence and fully in line with what Python has been doing since version 1.6, ie. U=U+U and U=U+8 (to use /Fs notation). > IMO, it is subversive to start taking new string functions/methods and > coercing their results to Unicode. I don't understand... there's nothing subversive here. If strings meet Unicode the result gets coerced to Unicode. Nothing surprising here. Why are you guys putting so much effort into fighting Unicode ? I often get the impression that you are considering Unicode a nightmare rather than a blessing. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 04 2004) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
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