Re: Python 3.x stuffing utf-8 into SQLite db

References	<CANc-5UwYdoPLKuqRbrfbOrQTVafOaZmWZ+8SnDc-TZp1NEXcQg@mail.gmail.com> <CAPTjJmpJV4KYcL50_=0hv+BLKaGX_X9wqQgMJeszMrHgAK+drA@mail.gmail.com>
Date	2015-02-09 11:30 -0600
Subject	Re: Python 3.x stuffing utf-8 into SQLite db
From	Skip Montanaro <skip.montanaro@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.18566.1423503049.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Sun, Feb 8, 2015 at 9:58 PM, Chris Angelico <rosuav@gmail.com> wrote:
> Those three characters are the CP-1252 decode of the bytes for U+2019
> in UTF-8 (E2 80 99). Not sure if that helps any, but given that it was
> an XLSX file, Windows codepages are reasonably likely to show up.

Thanks, Chris. Are you telling me I should have defined the input file
encoding for my CSV file as CP-1252, or that something got hosed on
the export from XLSX to CSV? Or something else?

Skip

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Python 3.x stuffing utf-8 into SQLite db Skip Montanaro <skip.montanaro@gmail.com> - 2015-02-09 11:30 -0600

csiph-web