Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #112342 > unrolled thread
| Started by | Malcolm Greene <python@bdurham.com> |
|---|---|
| First post | 2016-08-04 14:47 -0400 |
| Last post | 2016-08-04 14:47 -0400 |
| 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.
Capturing the bad codes that raise UnicodeError exceptions during decoding Malcolm Greene <python@bdurham.com> - 2016-08-04 14:47 -0400
| From | Malcolm Greene <python@bdurham.com> |
|---|---|
| Date | 2016-08-04 14:47 -0400 |
| Subject | Capturing the bad codes that raise UnicodeError exceptions during decoding |
| Message-ID | <mailman.170.1470336428.6033.python-list@python.org> |
I'm processing a lot of dirty CSV files and would like to track the bad codes that are raising UnicodeErrors. I'm struggling how to figure out what the exact codes are so I can track them, them remove them, and then repeat the decoding process for the current line until the line has been fully decoded so I can pass this line on to the CSV reader. At a high level it seems that I need to wrap the decoding of a line until it passes with out any errors. Any suggestions appreciated. Thank you, Malcolm
Back to top | Article view | comp.lang.python
csiph-web