lac at openend.se
Wed May 25 23:41:53 CEST 2011
This just in from pypy-dev. I am reposting it here because I
am fairly certain that nobody on the pypy-dev mailing list
uses the multibytecodex, but there has got to be at least one
person here who does.
Please reply to the pypy-dev article, not here, or mail to pypy-dev at python.org
if you are not on the pypy-dev mailing list (but have delivery turned off
as many of you do.)
------- Forwarded Message
From: Armin Rigo <arigo at tunes.org>
Date: Wed, 25 May 2011 21:39:35 +0200
To: pypy-dev at python.org
Subject: [pypy-dev] multibytecodec: missing features
Here are the missing features in multibytecodec:
* support for ``errors !=3D "strict"''.
* classes MultibyteIncrementalEncoder, MultibyteIncrementalDecoder,
MultibyteStreamReader and MultibyteStreamWriter.
One reason I didn't implement the classes yet is that I couldn't
understand two points in how they are supposed to work. But it seems
that there are really two bugs, as I've been pointed to:
http://bugs.python.org/issue12171 . So the question is if we should
be bug-compatible with Python 2.7 or if we should instead implement
some fixed version.
I suppose I'm rather for the fixed version, but I'd like to hear some
feedback from people that actually use multibytecodecs. Also, I
wouldn't mind if someone would pick up the work and just do it, either
the classes or ``errors !=3D "strict"'' :-)
pypy-dev mailing list
pypy-dev at python.org
------- End of Forwarded Message
More information about the Python-Dev