On Fri, 26 Dec 2014 23:17:12 +0100 Ivan Vilata i Balaguer <i...@selidor.net> wrote: > Ivan Vilata i Balaguer (2014-12-26 22:42:15 +0100) wrote: > > > [â¦] Maybe it's some kind on encoding problem. If I dump the database, > > I can see that the context is always escaped using ``\u`` (even if > > ``\x`` was enough), i.e. it has become ``aix\u00f2``. There should be > > no need of such escaping since JSON documents are UTF-8 native, so > > this only adds a chance for encoding errors. [â¦] > > Please ignore this, I already checked that this escaping is also native > for JSON to fit in ASCII encoding. :-/
Hi, Ivan. Sorry for the very late reply. We think the 2to3 conversion we're doing right now will fix this bug. We'll be making a new release eminently. jamie.
signature.asc
Description: PGP signature
