Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #91460 > unrolled thread

Re: Fwd: Lossless bulletproof conversion to unicode (backslashing) (fwd)

Started byanatoly techtonik <techtonik@gmail.com>
First post2015-05-29 17:41 +0300
Last post2015-05-29 17:41 +0300
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.


Contents

  Re: Fwd: Lossless bulletproof conversion to unicode (backslashing) (fwd) anatoly techtonik <techtonik@gmail.com> - 2015-05-29 17:41 +0300

#91460 — Re: Fwd: Lossless bulletproof conversion to unicode (backslashing) (fwd)

Fromanatoly techtonik <techtonik@gmail.com>
Date2015-05-29 17:41 +0300
SubjectRe: Fwd: Lossless bulletproof conversion to unicode (backslashing) (fwd)
Message-ID<mailman.182.1432910518.5151.python-list@python.org>
On Fri, May 29, 2015 at 2:39 PM, Laura Creighton <lac@openend.se> wrote:
> Do you know about the codecs module?
>
> reading http://pymotw.com/2/codecs/ may be useful if this is new to you.

Does that work for Python 2 and Python 3?

> Have you read https://www.python.org/dev/peps/pep-0293/ ?

No.

> Will backslashreplace do what you want?

I don't know. I am sorry, but what is there the code that
does this:

  binary -> escaped utf-8 string -> unicode -> binary

I know about coding module, but I am not seeing a solution
to crash-proof output from Python. Is inserting a custom codec
class into every piece of code that I want to debug is the only
solution?
-- 
anatoly t.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web