Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #85434 > unrolled thread
| Started by | Skip Montanaro <skip.montanaro@gmail.com> |
|---|---|
| First post | 2015-02-09 12:52 -0600 |
| Last post | 2015-02-09 12:52 -0600 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Python 3.x stuffing utf-8 into SQLite db Skip Montanaro <skip.montanaro@gmail.com> - 2015-02-09 12:52 -0600
| From | Skip Montanaro <skip.montanaro@gmail.com> |
|---|---|
| Date | 2015-02-09 12:52 -0600 |
| Subject | Re: Python 3.x stuffing utf-8 into SQLite db |
| Message-ID | <mailman.18601.1423555315.18130.python-list@python.org> |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Feb 9, 2015 at 11:54 AM, Matthew Ruffalo <mmr15@case.edu> wrote: > I think it's most likely that the encoding issues happened in the export > from XLSX to CSV (unless the data is malformed in the original XLSX > file, of course). Aha! Lookee here... (my apologies to all you HTML mail haters - sometimes it even comes in handy. :-) This snapshot was taken against a running LibreOffice instance here at work (on Linux). It would appear the fancy schmancy apostrophe was hosed up before the data ever got to me. Had a guy here with Windows pop up the original file I got in an actual Excel instance. Same bogosity. Knowing that, I don't feel the least bit timid about just editing the darn CSV file to correct the encode/decode/encode error before loading the data into SQLite. I was worried that since I was doing some Python 3.x stuff involving Unicode for the first time that I'd screwed something up. Skip
Back to top | Article view | comp.lang.python
csiph-web