Message172134
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. |
|
Date |
User |
Action |
Args |
2012-10-05 20:39:01 | skrah | set | recipients:
+ skrah, pitrou, rogerbinns, Arfrever |
2012-10-05 20:39:01 | skrah | set | messageid: <1349469541.44.0.515339179545.issue16145@psf.upfronthosting.co.za> |
2012-10-05 20:39:01 | skrah | link | issue16145 messages |
2012-10-05 20:39:01 | skrah | create | |
|