[pypy-issue] Issue #1815: gdbm does not implicitly coerce unicode (pypy/pypy)

Julian Berman issues-reply at bitbucket.org
Mon Jul 7 23:04:12 CEST 2014

Previous message: [pypy-issue] Issue #1814: gdbm.error only sets message, not errno (pypy/pypy)
Next message: [pypy-issue] [Bitbucket] Issue #1815: gdbm does not implicitly coerce unicode (pypy/pypy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

New issue 1815: gdbm does not implicitly coerce unicode
https://bitbucket.org/pypy/pypy/issue/1815/gdbm-does-not-implicitly-coerce-unicode

Julian Berman:

On CPython, gdbm coerces Unicode keys to ASCII. PyPy's gdbm only checks for str, and throws a TypeError.

Previous message: [pypy-issue] Issue #1814: gdbm.error only sets message, not errno (pypy/pypy)
Next message: [pypy-issue] [Bitbucket] Issue #1815: gdbm does not implicitly coerce unicode (pypy/pypy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the pypy-issue mailing list