On Tue, Apr 12, 2016 at 9:20 AM, Chris Angelico <rosuav at gmail.com> wrote: > > latin1? I thought latin1 had a code point for 0-255, so how could using > it > > raise an encoding error? > > Latin-1 / ISO-8859-1 defines a character for every byte, so any byte > string will *decode*. It only defines 256 characters as having > equivalent bytes, though, so *encoding* can fail. > unless it was decoded as latin-1 in the first place. doesn't the surrogate escape thing only work properly if you decode/encode with the same encoding? -CHB Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160412/01074b98/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4