Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #18668
| From | Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: How to support a non-standard encoding? |
| Date | 2012-01-08 12:16 +0100 |
| Organization | A newly installed InterNetNews server |
| Message-ID | <jebtu9$5m2$1@r03.glglgl.gl> (permalink) |
| References | <je6guf$pns$1@localhost.localdomain> <1480875f-d133-40a1-8fd1-dd31a2dd430b@d10g2000vbh.googlegroups.com> |
Am 06.01.2012 21:00 schrieb jmfauth: > Another simple approach, os independent. > > You probably do not write your code in iso-6937, but > you only need to encode/decode some bytes sequence > "on the fly". In that case, work with bytes, create > a couple of coding / decoding functions with a > created<dict> [*] as helper. It's not so complicate. > Use<unicode> Py2 or<str> Py3 (the recommended > way ;-) ) as pivot encoding. These coding/decoding functions are exactly the way to create a codec. I. e., it is not much more. Thomas
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
How to support a non-standard encoding? Ivan <ivan@llaisdy.com> - 2012-01-06 10:03 +0000
Re: How to support a non-standard encoding? Tim Wintle <tim.wintle@teamrubber.com> - 2012-01-06 13:47 +0000
Re: How to support a non-standard encoding? Ivan Uemlianin <ivan@llaisdy.com> - 2012-01-06 14:03 +0000
Re: How to support a non-standard encoding? jmfauth <wxjmfauth@gmail.com> - 2012-01-06 12:00 -0800
Re: How to support a non-standard encoding? Tim Wintle <tim.wintle@teamrubber.com> - 2012-01-06 20:42 +0000
Re: How to support a non-standard encoding? Ivan <ivan@llaisdy.com> - 2012-01-08 08:50 +0000
Re: How to support a non-standard encoding? Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2012-01-08 12:16 +0100
csiph-web