Stefan Krah added the comment:
In general APSW does not look ready for the Python 3.3 Unicode
implementation. Example: src/statementcache.c:217
Py_UNICODE *out;
PyObject *res=PyUnicode_FromUnicode(NULL, size);
Python 3.3 docs:
"If the buffer is NULL, PyUnicode_READY() must be called once the string
content has been filled before using any of the access macros such as
PyUnicode_KIND()."
The abort() in the traceback occurs precisely because PyUnicode_READY()
hasn't been called, so I'm closing this as invalid.
----------
nosy: +skrah
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16145>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
