On Wed, May 25, 2011 at 12:39 PM, Armin Rigo <[email protected]> wrote:
> Hi all, > > Here are the missing features in multibytecodec: > > * support for ``errors != "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/issue12100 and > 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 != "strict"'' :-) > > > A bientôt, > > Armin. > _______________________________________________ > pypy-dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/pypy-dev > Victor has fixed one of these bugs, so at least I don't think we should be "bug compatible" with it. Also, if people like my idea of trying to do a PyPy 1.5.1 right after CPython 2.7.2 (RC1 scheduled for the 28th) it would be easy to start pulling in the stdlib now to not deal with it. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero
_______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
