On Tuesday 20 March 2007 21:17, Carsten Haese
wrote:
> On Tue, 2007-03-20 at 20:26 -0400, jim-on-linux
wrote:
> > I have been getting the same thing using
> > SQLite3 when extracting data fron an SQLite3
> > database.
>
> Many APIs that exchange data choose to exchange
> text in Unicode because t
On Tue, 2007-03-20 at 20:26 -0400, jim-on-linux wrote:
> I have been getting the same thing using SQLite3
> when extracting data fron an SQLite3 database.
Many APIs that exchange data choose to exchange text in Unicode because
that eliminates encoding uncertainty. Whether an API uses Unicode woul
On Tue, 2007-03-20 at 16:47 -0700, Gerry wrote:
> I'm still mystified why:
>qno was ever unicode,
Thus quoth http://www.lexicon.net/sjmachin/xlrd.html "This module
presents all text strings as Python unicode objects."
-Carsten
--
http://mail.python.org/mailman/listinfo/python-list
On Tuesday 20 March 2007 18:35, Gerry wrote:
> I'm using pyExcelerator and xlrd to read and
> write data from and to two spreadsheets.
>
> I created the "read" spreadsheet by importing a
> text file - and I had no unicode aspirations.
>
> When I read a cell, it appears to be unicode
> u'Q1", say.
>
En Tue, 20 Mar 2007 20:47:22 -0300, Gerry <[EMAIL PROTECTED]>
escribió:
> Thanks! - that helps a lot.
>
> I'm still mystified why:
>qno was ever unicode, and why
I can't tell...
>qno.encode("ascii", "replace") is still unicode.
That *returns* a string, but you are discarding the retur
On Mar 20, 7:29 pm, "Gabriel Genellina" <[EMAIL PROTECTED]>
wrote:
> En Tue, 20 Mar 2007 19:35:00 -0300, Gerry <[EMAIL PROTECTED]>
> escribió:
>
Thanks! - that helps a lot.
I'm still mystified why:
qno was ever unicode, and why
qno.encode("ascii", "replace") is still unicode.
Gerry
>
>
En Tue, 20 Mar 2007 19:35:00 -0300, Gerry <[EMAIL PROTECTED]>
escribió:
> which seems to work. Here's the mysterious part (aside from why
> anything was unicode in the first place):
>
> print >> debug, "c=", col, "r=", row, "v=", value,
> "qno=", qno
> tuple = (q
