Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #56700
| From | Piet van Oostrum <piet@vanoostrum.org> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Unicode Objects in Tuples |
| Date | 2013-10-11 14:44 -0400 |
| Message-ID | <m2a9ifsl45.fsf@cochabamba.vanoostrum.org> (permalink) |
| References | <CAP=-cKU6Xkt_rm4VYh7NfXLSfUDG7FZQXHz+U12gP6fbkdhxbQ@mail.gmail.com> <5257C35C.4070407@nedbatchelder.com> <mailman.1004.1381499974.18130.python-list@python.org> |
Stephen Tucker <stephen_tucker@sil.org> writes: > ESRI compound the problem, actually, by making all the strings that the ArcGIS Python interface > delivers (from MS SQLServer) Unicode! (I suppose, on reflection, they have no choice.) So I am > stuck with the worst of both worlds - a generation of Python (2.X) that is inept at handling > unicode (on an operating system (MS Windows 7) that is not much better, and being flooded with > unicode strings from my users' databases! Anything you can come up with to ease all this (like, > "convert all your strings to unicode as soon as you can and render them as ASCII as late as you > can") has already been of help. I wouldn't say that Python 2.x is inept at handling Unicode. You just have to know what you are doing. But that's also true for Python 3.x, although that give you a bit more help. But you can do everything you want with 2.x, I think. -- Piet van Oostrum <piet@vanoostrum.org> WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4]
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: Unicode Objects in Tuples Stephen Tucker <stephen_tucker@sil.org> - 2013-10-11 14:31 +0100 Re: Unicode Objects in Tuples Piet van Oostrum <piet@vanoostrum.org> - 2013-10-11 14:44 -0400
csiph-web